docs/diploma

annotate thesis/tex/4-MasqmailsFuture.tex @ 226:99ad9d520add

find changesets by author, revision, files, or words in the commit message
Added tag proof-read version for ben and james (ch234) for changeset 47af8eb539cf
author meillo@marmaro.de
date Tue, 06 Jan 2009 19:00:14 +0100
parents 5adc26977dc6
children 1afdb3f85e69
rev   line source
meillo@109 1 \chapter{\masqmail's present and future}
meillo@93 2
meillo@185 3 This chapter \dots %fixme write text here
meillo@185 4
meillo@185 5
meillo@185 6
meillo@185 7
meillo@137 8 \section{Existing code base}
meillo@185 9
meillo@142 10 Here regarded is version 0.2.21 of \masqmail. This is the last version released by Oliver \person{Kurth}, and the basis for my thesis.
meillo@142 11
meillo@93 12
meillo@185 13 \subsubsection*{The source code}
meillo@185 14
meillo@219 15 \masqmail\ is written in the C programming language. The program, as of version 0.2.21, consists of 34 source code and eight header files, containing about 9,000 lines of code\footnote{Measured with \name{sloccount} by David A.\ Wheeler.}. Additionally, it includes a \name{base64} implementation (about 300 lines) and \name{md5} code (about 150 lines). For systems that do not provide \name{libident}, this library is distributed as well (circa 600 lines); an available shared library has higher precedence in linking, though.
meillo@185 16
meillo@219 17 The only mandatory dependency is \name{glib}---a cross-platform software utility library, originated in the \NAME{GTK+} project. It provides safe replacements for many standard library functions, especially for the string functions. It also offers handy data containers, easy-to-use implementations of data structures, and much more.
meillo@185 18
meillo@225 19 With \masqmail\ comes the small tool \path{mservdetect}; it helps setting up a configuration that uses the \name{mserver} system to detect the online state. Two other binaries get compiled for testing purposes: \path{readtest} and \path{smtpsend}. All three programs use \masqmail\ source code; they only add a file with a \verb+main()+ function each.
meillo@185 20
meillo@219 21 \masqmail\ lacks an interface to plug in modules with additional functionality. There exists no add-on or module system. The code is only separated by function to the various source files. Some functional parts can be included or excluded by defining symbols at compile time. Adding maildir support, means giving the option \verb+--enable-maildir+ to the \path{configure} call. This preserves the concerning code to get removed by the preprocessor. Unfortunately the \verb+#ifdef+s are scattered through all the source, leading to code that is hard to read.
meillo@185 22 %fixme: refer to ifdef-considered-harmful ?
meillo@185 23
meillo@185 24
meillo@185 25
meillo@137 26 \subsubsection*{Features}
meillo@219 27 \label{sec:masqmail-features}
meillo@93 28
meillo@225 29 \masqmail\ accepts mail on the command line and via \SMTP. Mail queuing and alias expansion is supported. \masqmail\ is able to deliver mail to local mailboxes (in \name{mbox} or \name{maildir} format) or pass it to a \name{mail delivery agent} (like \name{procmail}). Mail for remote destinations is sent using \SMTP\ or can be piped to commands, that are gateways to \NAME{UUCP} or telefax for example.
meillo@93 30
meillo@219 31 Outgoing \SMTP\ connections feature \SMTP-\NAME{AUTH} and \SMTP-after-\NAME{POP} authentication, but incoming connections do not. Using wrappers for outgoing connections is supported. This allows encrypted communication through a wrapper application like \name{openssl}.
meillo@137 32 %todo: what about SSL/TLS encryption?
meillo@93 33
meillo@225 34 \masqmail\ focuses on non-permanent online connections, thus a concept of online routes is used. One may configure any number of routes to send mail. Each route can have criteria, like matching \texttt{From:} or \texttt{To:} headers, to determine if some message is allowed to be sent over it. Mail to destinations outside the local network gets queued until an online connections is available.
meillo@142 35
meillo@225 36 The \masqmail\ executable can be called under various names for sendmail-compatibility reasons. This is organized by symbolic links with different names pointing to the \masqmail\ executable. The \sendmail\ names are \path{/usr/lib/sendmail} and \path{/usr/sbin/sendmail} because many programs expect the \mta\ to be located there. Further more \sendmail\ supports calling it with a different name instead of supplying command line arguments. The best known of this shortcuts is \path{mailq}, which is equivalent to calling it with the argument \verb+-bq+. \masqmail\ recognizes the names \path{mailq}, \path{smtpd}, \path{mailrm}, \path{runq}, \path{rmail}, and \path{in.smtpd}. The first two are inspired by \sendmail. Not implemented is the name \path{newaliases} because \masqmail\ does not generate binary representations of the alias file.\footnote{A shell script named \path{newaliases}, that invokes \texttt{masqmail -bi}, can provide the command to satisfy other software needing it.} \path{hoststat} and \path{purgestat} are missing for complete sendmail-compatibility.
meillo@109 37 %masqmail: mailq, mailrm, runq, rmail, smtpd/in.smtpd
meillo@109 38 %sendmail: hoststat, mailq, newaliases, purgestat, smtpd
meillo@109 39
meillo@219 40 Additional to the \mta\ job, \masqmail\ also offers mail retrieval services by being a \NAME{POP3} client. It can fetch mail from different remote locations, dependent on the active online connection.
meillo@109 41
meillo@137 42
meillo@132 43
meillo@132 44
meillo@132 45
meillo@132 46
meillo@177 47 \section{Requirements}
meillo@219 48 \label{sec:mta-requirements}
meillo@146 49
meillo@185 50 This section identifies the requirements for a modern \masqmail. Most of them will apply to modern \MTA{}s in general.
meillo@185 51
meillo@218 52
meillo@185 53
meillo@177 54
meillo@219 55 \subsection{Functional requirements}
meillo@146 56
meillo@225 57 The basic job of a \mta\ is to transport mail from senders to recipients. This is the definition of such kind of software, and this is how \MTA{}s are generally seen \cite[page 19]{dent04} \cite[pages 3-5]{hafiz05}.
meillo@219 58
meillo@219 59 An \MTA\ therefore needs at least a mail receiving facility and a mail sending facility.
meillo@219 60
meillo@219 61
meillo@219 62
meillo@219 63 \subsubsection*{Incoming channels}
meillo@219 64
meillo@219 65 \sendmail-compatible \mta{}s must support at least two incoming channels: mail submitted using the \sendmail\ command, and mail received on a \NAME{TCP} port. Thus it is common to split the incoming channels into local and remote. This is done by \qmail\ and \postfix. The same way is \person{Hafiz}'s view. \SMTP\ is the primary mail transport protocol today, but with the increasing need for new protocols\ref{FIXME} in mind, support for more than just \SMTP\ is good to have. This leads to multiple remote channels.
meillo@219 66
meillo@219 67
meillo@219 68 \subsubsection*{Outgoing channels}
meillo@219 69
meillo@219 70 Outgoing mail is commonly either sent using \SMTP, piped into local commands (for example \path{uucp}), or delivered locally by appending to a mailbox.
meillo@219 71
meillo@219 72 Outgoing channels are similar for \qmail, \postfix, and \name{sendmail X}: All of them have a module to send mail using \SMTP, and one for writing into a local mailbox.
meillo@219 73
meillo@219 74 % is the def of MTA: transfer between machines, or transfer between users?
meillo@225 75 Local mail delivery is a job that requires root privilege to be able to switch to any user in order to write to his mailbox. As mail delivery to local users, is \emph{not} included in the basic job of an \MTA{}, why should it care about it? In order to reduce root privilege, to keep the system simple, and to have programs that do one job well, the local delivery job should be handed over to a specialist: a \name{mail delivery agent}. \NAME{MDA}s know about the various mailbox formats and are aware of the problems of concurrent write access and the like. Hence passing the message, and the responsibility for it, over to an \NAME{MDA}, like \name{procmail} or \name{maildrop}, seems to be best.
meillo@219 76
meillo@225 77 This means an outgoing connection that pipes mail into local commands is required. Other outgoing channels, one for each supported protocol, may be designed like it was done in other \MTA{}s.
meillo@219 78
meillo@219 79
meillo@219 80
meillo@219 81 \subsubsection*{Mail queue}
meillo@219 82
meillo@225 83 Additionally to the mail receiving and sending facilities, mail queuing is a basic feature. A mail queue removes the need to deliver instantly as a message is received. It provides fail-safe storage of mails until they are delivered. Mail queues are probably used in all \mta{}s, excluding the simple forwarders. The mail queue is essential for \masqmail, as \masqmail\ is used for non-permanent online connections. This means, mail must be queued until a online connection is available to send the message. This may be after a reboot.
meillo@219 84
meillo@219 85 The mail queue and the module(s) to manage it are the central part of the whole system. This demands especially for robustness and reliability, as a failure here can lead to loosing mail. An \MTA\ takes over responsibility for mail in accepting it, hence loosing mail messages is absolutely to avoid. This covers any kind of crash situation too. The worst thing acceptable to happen is an already sent mail to be sent again.
meillo@219 86
meillo@219 87
meillo@219 88
meillo@219 89
meillo@219 90 \subsubsection*{Header sanitizing}
meillo@219 91
meillo@219 92 Mail coming into the system often lacks important header lines. At least the required ones must be added by the \MTA. One example is the \texttt{Date:} header, another is the, not required but recommended, \texttt{Message-ID:} header. Apart from adding missing headers, rewriting headers is important too. Changing the locally known domain part of email addresses to globally known ones is an example. \masqmail\ needs to be able to rewrite the domain part dependent on the route used to send the message, to prevent messages to get classified as spam.
meillo@219 93
meillo@225 94 Generating the envelope is a related job. The envelope specifies the actual recipient of the mail, no matter what the \texttt{To:}, \texttt{Cc:}, and \texttt{Bcc:} headers contain. Multiple recipients lead to multiple different envelopes, containing all the same mail message.
meillo@219 95
meillo@219 96
meillo@219 97
meillo@219 98
meillo@219 99 \subsubsection*{Aliasing}
meillo@219 100
meillo@225 101 Email addresses can have aliases, thus they need to be expanded. Aliases can be of different kind: another local user, a remote user, a list containing local and remote users, or a command. Most important are the aliases in the \path{aliases} file, usually located at \path{/etc/aliases}. Addresses expanding to lists of users lead to more envelopes. Aliases changing the recipient's domain part may require a different route to be used.
meillo@219 102
meillo@219 103
meillo@219 104
meillo@219 105
meillo@219 106 \subsubsection*{Selecting a route}
meillo@219 107
meillo@219 108 One key feature of \masqmail\ is its ability to send mail out over different routes. The decision, which route to take, is based on the current online state and whether a route may be used for a message or not. The online state can be retrieved in tree ways, explained in \ref{sec:fixme}. A route is chosen by checking every available route for being able to transfer the current message, until one matches.
meillo@219 109
meillo@219 110
meillo@219 111
meillo@219 112
meillo@219 113 \subsubsection*{Authentication}
meillo@219 114
meillo@219 115 One thing to avoid is being an \name{open relay}. Open relays allow to relay mail from everywhere to everywhere. This is a source of spam. The solution is restricting relay\footnote{Relaying is passing mail, that is not from and not for the own system, through it.} access.
meillo@219 116
meillo@225 117 Several ways to restrict access are available. The most simple one is restriction by the \NAME{IP} address. No extra complexity is added this way, but static \NAME{IP} addresses are required.
meillo@219 118
meillo@219 119 If static access restriction is not possible, some kind of authentication mechanism is required. Three common kinds exist:
meillo@219 120 \begin{itemize}
meillo@219 121 \item \SMTP-after-\NAME{POP}: Uses authentication on the \NAME{POP} protocol to permit incoming \SMTP\ connections for a limited time afterwards.
meillo@219 122 \item \SMTP\ authentication: An extension to \SMTP. It allows to request authentication before mail is accepted.
meillo@219 123 \item Certificates: The identity is confirmed by certificates that are signed by trusted authorities.
meillo@219 124 \end{itemize}
meillo@219 125
meillo@219 126
meillo@219 127
meillo@219 128 \subsubsection*{Encryption}
meillo@219 129
meillo@219 130 Electronic mail is very weak to sniffing attacks, because all data transfer is unencrypted. This concerns the message's content, as well as the email addresses in header and envelope, but also authentication dialogs that transfer plain text passwords (\NAME{PLAIN} and \NAME{LOGIN} are examples). Hence encryption is wanted.
meillo@219 131
meillo@219 132 The common way to encrypt \SMTP\ dialogs is using \name{Transport Layer Security} (short: \TLS, successor of \NAME{SSL}). \TLS\ encrypts the datagrams of the \name{transport layer}. This means it works below the application protocols and can be used by any of them \citeweb{wikipedia:tls}.
meillo@219 133
meillo@219 134 Outgoing \SMTP\ connections can get encrypted using a secure tunnel, created by an external application. Incoming connections, can not use this technique because the remote \NAME{IP} address is hidden then; \NAME{STARTTLS}---defined in \RFC2487---is what \mta{}s usually implement.
meillo@219 135
meillo@219 136
meillo@219 137
meillo@219 138 \subsubsection*{Spam prevention}
meillo@219 139
meillo@219 140 Spam is a major threat nowadays, but it is a war that is hard to win. The goal is to provide state-of-the-art spam protection, but not more (see section \ref{sec:swot-analysis}).
meillo@219 141
meillo@225 142 As spam is not just a nuisance for end users, but also for the infrastructure---the \mta{}s---by increasing the amount of mail messages, \MTA{}s need to protect them self.
meillo@219 143
meillo@219 144 Filtering spam can be done in two ways: Refusing spam during the \SMTP\ dialog or checking for spam after the mail was accepted and queued. Both have advantages and disadvantages, so modern \MTA{}s use them in combination. Spam is identified by the results of a set of checks. Static rules, querying databases (\NAME{DNS} blacklists), requesting special client behavior (\name{greylisting}, \name{hashcash}), or statistical analysis (\name{bayesian filters}) are checks that may be used. Running more checks leads to better results, but takes more system resources and more time.
meillo@219 145
meillo@219 146 Doing some basic checks during the \SMTP\ dialog seems to be a must.
meillo@219 147
meillo@219 148
meillo@219 149
meillo@219 150 \subsubsection*{Virus checking}
meillo@219 151
meillo@225 152 Related to spam is malicious content (short: \name{malware}) like viruses, worms, trojan horses. They, in contrast to spam, do not affect the \MTA\ itself, as they are in the mail's body. \MTA{}s searching for malware is equal to real world's post offices opening letters to check if they contain something that could harm the recipient. This is not a mail transport job. But the \MTA\ responsible for the recipient seems to be at a good position to do this work, so it is often done there.
meillo@219 153
meillo@219 154 In any way should malware checking be performed by external programs that may be invoked by the \mta. But using mail deliver agents, like \name{procmail}, are better suited locations to invoke content scanners.
meillo@219 155
meillo@219 156 A popular email filter framework is \name{amavis} which integrates various spam and virus scanners. The common setup includes a receiving \MTA\ which sends it to \name{amavis} using \SMTP, \name{amavis} processes the mail and sends it then to a second \MTA\ that does the outgoing transfer. Having interfaces to such scanners is nice to have, though.
meillo@219 157
meillo@219 158
meillo@219 159
meillo@219 160 \subsubsection*{Archiving}
meillo@219 161
meillo@219 162 Mail archiving and auditability become more important as email establishes as technology for serious business communication. The ability to archive verbatim copies of every mail coming into and every mail going out of the system, with relation between them, appears to be a goal to achieve.
meillo@219 163
meillo@225 164 \postfix\ for example has a \texttt{always\_bcc} feature, to send a copy of every outgoing mail to a definable recipient. At least this functionality should be given, although a more complete approach is preferable.
meillo@219 165
meillo@219 166
meillo@219 167
meillo@219 168
meillo@219 169
meillo@219 170 \subsection{Non-functional requirements}
meillo@219 171
meillo@225 172 Here follows a list of non-functional requirements for \masqmail. These requirements specify the quality properties of software. The list is based on \person{Hafiz} \cite[page~2]{hafiz05}, with inspiration from \person{Spinellis} \cite[page~6]{spinellis06} and \person{Kan} \cite{kan03}.
meillo@185 173 %fixme: refer to ch01 and ch02
meillo@146 174
meillo@146 175
meillo@177 176 \subsubsection*{Security}
meillo@225 177 \MTA{}s are critical points for computer security, as they are accessible from external networks. They must be secured with high effort. Properties like the need for high privilege level, from outside influenced work load, work on unsafe data, and demand for reliability, increase the need for security. \masqmail\ needs to be secure enough for its target field of operation.
meillo@177 178
meillo@177 179
meillo@177 180 \subsubsection*{Reliability}
meillo@196 181 Reliability is the second essential quality property for an \MTA. Mail for which the \MTA\ took responsibility must never get lost. The \MTA\ must not be \emph{the cause} of any mail loss, no matter what happens. Unreliable \mta{}s are of no value.
meillo@177 182
meillo@189 183
meillo@189 184 \subsubsection*{Robustness}
meillo@219 185 Being robust means handling errors properly. Small errors may get corrected, large errors may kill a process. Killed processes should restarted automatically and lead to a clean state again. Log messages should be written in every case. Robust software does not need a special environment, it creates a friendly environment itself. \person{Raymond}'s \name{Rule of Robustness} and his \name{Rule of Repair} are good descriptions \cite[pages~18--21]{raymond03}.
meillo@177 186
meillo@177 187
meillo@177 188 \subsubsection*{Extendability}
meillo@219 189 \masqmail's architecture needs to be extendable, to allow new features to be added afterwards. The reason for this need are changing requirements. New requirements appear, like more efficient mail transfer of large messages or a final solution for spam problem. Extendability is the ability of software to include new function with little work.
meillo@196 190
meillo@146 191
meillo@189 192 \subsubsection*{Maintainability}
meillo@219 193 Maintaining software takes much time and effort. \person{Spinellis} guesses ``40\,\% to 70\,\% of the effort that goes into a software system is expended after the system is written first time.'' \cite[page~1]{spinellis03}. This work is called \emph{maintaining}. Hence making software good to maintain will ease work afterwards.
meillo@146 194
meillo@189 195
meillo@189 196 \subsubsection*{Testability}
meillo@225 197 Good testability make maintenance easier too, because functionality is directly verifiable when changes are done, thus removing uncertainty. Modularized software makes testing easier, because parts can be tested without external influences. \person{Spinellis} sees testability as a sub-quality of maintainability.
meillo@189 198
meillo@189 199
meillo@189 200 \subsubsection*{Performance}
meillo@196 201 Also called ``efficiency''. Efficient software requires few time and few resources. The merge of communication hardware and its move from service providers to homes and to mobile devices, demand smaller and more resource-friendly software. The amount of mail will be lower, even if much more mail will be sent. More important will be the energy consumption and heat emission. These topics increased in relevance during the past years and they are expected to become more central.
meillo@146 202
meillo@146 203
meillo@189 204 \subsubsection*{Availability}
meillo@225 205 Availability is important for server programs. They must stay operational by blocking \name{denial of service} attacks and the like.
meillo@146 206
meillo@146 207
meillo@189 208 \subsubsection*{Portability}
meillo@225 209 Source code that compiles and runs on various operation systems is called portable. Portability can be achieved by using standard features of the programming language and common libraries. Basic rules to achieve portable code are defined by \person{Kernighan} and \person{Pike} \cite{kernighan99}. Portable code lets software spread faster.
meillo@189 210
meillo@189 211
meillo@189 212 \subsubsection*{Usability}
meillo@219 213 Usability, not mentioned by \person{Hafiz} (he focuses on architecture) but by \person{Spinellis} and \person{Kan}, is a property very important from the user's point of view. Software with bad usability is rarely used, no matter how good it is. If substitutes with better usability exist, the user will switch to one of them. Here, usability includes setting up and configuring; and the term ``users'' includes administrators. Having \mta{}s on home servers and workstations requires easy and standardized configuration. The common setups should be configurable with little action by the user. Complex configuration should be possible, but focused must be the most common form of configuration: choosing one of several common setups.
meillo@185 214
meillo@185 215
meillo@185 216
meillo@185 217
meillo@185 218
meillo@185 219
meillo@185 220
meillo@185 221
meillo@185 222 \section{Work to do}
meillo@185 223
meillo@219 224 After \masqmail's features were presented in section \ref{sec:masqmail-features} and the requirements for modern \mta{}s were identified in section \ref{sec:mta-requirements}, here the differences between them are shown.
meillo@185 225
meillo@185 226
meillo@187 227
meillo@187 228 \subsubsection*{Fulfilled requirements}
meillo@187 229
meillo@219 230 \masqmail's incoming and outgoing channels are the ones common to most \MTA{}s: the \path{sendmail} command and \SMTP\ for incoming mail; local delivery, piping to commands, and \SMTP\ for outgoing mail. Support for other protocols is not available. To add it, modifications at many places in the source are needed.
meillo@187 231
meillo@219 232 One single mail queue is used in \masqmail. The envelope and mail headers are generated when the mail is put into the queue. Aliasing is done on delivery, after the route to be used was determined. Headers can get rewritten then. These parts do all provide the functionality required.
meillo@187 233
meillo@219 234 Static authentication, based on \NAME{IP} addresses, can be with \person{Venema}'s \NAME{TCP} \name{Wrapper}, by editing the \path{hosts.allow} and \path{hosts.deny} files. Dynamic \SMTP\ authentication is supported in form of \NAME{SMTP-AUTH} and \SMTP-after-\NAME{POP}, but only for outgoing channels. Similar for encryption which is also only available for outgoing channels; here a wrapper application like \name{openssl} is needed. Support for authentication and encryption of incoming connections is completely missing, although it is a basic requirement for secure emailing.
meillo@187 235
meillo@219 236 \masqmail\ does not provide special support for spam filtering and content checking. But it is possible to use external filter applications by running two independent instances of \masqmail, connected by the filter application. The receiving \MTA\ instance accepts mail and pushes it into the filter application. The filter application receives mail, processes it, possible modifies it, and pushes it to a second \MTA\ instance. The second \MTA\ is responsible for further delivery of the mail.
meillo@219 237 %Appendix \ref{app:FIXME} shows configuration files to create such a setup.
meillo@225 238 This is a concept that works in general. However, real spam \emph{prevention}---to not even accept spam---or good filter interfaces are not available. But they are necessary for using \masqmail\ in an unsafe environment.
meillo@187 239
meillo@187 240 There is currently no way of archiving every message going through \masqmail.
meillo@187 241
meillo@187 242
meillo@196 243 Non-functional requirements are not so easy to be marked as fulfilled or not. Instead they are discussed here.
meillo@196 244
meillo@219 245 \masqmail\ needs to be ``secure enough'', but what is ``secure enough''? This depends on its target field. Currently \masqmail\ is targeted to workstations and private networks, with explicit warning to not use it on permanent online hosts \citeweb{masqmail:homepage2}. \masqmail's current security is bad. For instance does a long time known attack against \sendmail, described by \person{Sill} \cite[page~4]{sill02}, still outwit \masqmail. Its security, however, seems acceptable for use on workstations and private networks, if the environment is trustable. In environments where untrusted components or persons have access to \masqmail, its security is too low.
meillo@196 246
meillo@196 247 Similar for its reliability. It has been reported that \masqmail\ has not sent mail under some circumstances \citeweb{FIXME}. %fixme
meillo@219 248 Situations where only one part of sent message was removed from the queue, and the other part remained as garbage, showed off, too---even to the author of this thesis. Fortunately, lost email was no big problem yet, but \person{Kurth} warns:
meillo@219 249 \begin{quote}
meillo@219 250 There may still be serious bugs in [masqmail], so mail might get lost. But in the nearly two years of its existence so far there was only one time a bug which caused mail retrieved via pop3 to be lost in rare circumstances.
meillo@219 251 \hfill\citeweb{masqmail:homepage2}
meillo@219 252 \end{quote}
meillo@219 253 In summary: Current reliability is not good enough.
meillo@196 254
meillo@219 255 The logging behavior of \masqmail\ is good, although it does not cover all problem situations. For example, if the queue directory is world writeable by accident (or as action of an intruder), any user can remove messages from the queue or replace them with own ones. \masqmail\ does not even write a debug message in this case. The origin of this problem, however, is \masqmail's trust in its environment.
meillo@196 256
meillo@219 257 \masqmail's extendability is very poor. This is a general problem of monolithic software, but can thus be provided with high effort. \exim\ is an example for good extendability in a monolithic program.
meillo@196 258
meillo@225 259 The maintainability of \masqmail\ appears to be equivalent to other software of similar kind. Missing modularity and therefore more complexity makes the maintainer's work harder. In summary is \masqmail's maintainability bearable, like in average Free Software projects. The testability suffers from missing modularity. Testing program parts is hard to do. Anyhow, it is done by compiling parts of the source to special test programs.
meillo@196 260
meillo@225 261 The performance---efficiency---of \masqmail\ is good enough for its target field of operation, where this is a minor goal. This applies equal to availability. Hence no further work needs to be done her.
meillo@196 262
meillo@225 263 The code's portability is good with view on \unix-like operation systems. At least \name{Debian}, \name{Red Hat}, \NAME{SUSE}, \name{Slackware}, \name{Free}\NAME{BSD}, \name{Open}\NAME{BSD}, and \name{Net}\NAME{BSD} are reported to be able to compile and run \masqmail\ \citeweb{masqmail:homepage2}. Special requirements for the underlying file system are not known. Therefore, the portability is already good.
meillo@196 264
meillo@225 265 The usability, from the administrator's point of view, is very good. \masqmail\ was developed to suite a specific, limited job---its configuration does perfect match. The user's view does not reach to the \MTA, as it is hidden behind the \name{mail user agent}.
meillo@196 266
meillo@187 267
meillo@187 268
meillo@187 269 \subsubsection*{Missing parts}
meillo@187 270
meillo@225 271 Support for other protocols than \SMTP\ seems not to be necessary at the moment. Adding such support will need lots of work in many parts of \masqmail. Hence delaying this work until the support becomes mandatory, appears to be the best strategy. This way work can be saved if some protocols never become popular.
meillo@187 272
meillo@225 273 Authentication of incoming \SMTP\ connections is definitely needed and should be added soon. The same applies to encryption of incoming connections. These two features are essential for restricting relaying and for providing privacy.
meillo@187 274
meillo@219 275 As authentication can be a guard against spam, filter facilities have lower priority. But basic spam filtering and interfaces for external tools should be implemented in future. Content checking should be left over to the \NAME{MDA}, to deal with it during local delivery.
meillo@187 276
meillo@225 277 Archiving again is preferred to be implemented soon. It does not require much work, but enables all kinds of statistical analysis.
meillo@187 278
meillo@200 279 Non-functional requirements need improvement too.
meillo@185 280
meillo@219 281 \masqmail's security is bad, thus the program is forced into a limited field of operation. The field of operation even shrinks, as security becomes more important and networking and interaction increases. Save and trusted environment become rare. Improving security is an important thing to do.
meillo@185 282
meillo@219 283 Reliability is also to improve. It is a key quality property for an \MTA, and not good enough in \masqmail. Additionally, the program is lacking robustness. Checking the environment and reporting bad characteristics is wanted. Especially improving robustness in relation to the queue is favorable; applying ideas of \name{crash-only software}\cite{candea03} will be a good step.
meillo@185 284
meillo@219 285 Extendability, maintainability, and testability do all suffer from the monolithic architecture and are nearly impossible to improve without changing the programs structure. These properties can hardly be retrofitted into software. Extendability might become important in the future. The other two ease all further work on the software, and also improve security and reliability.
meillo@185 286
meillo@225 287 Performance is a property that is nice to have. But as performance improvements are in contrast to many other quality properties (reliability, maintainability, usability, capability \cite[page~5]{kan03}), jeopardizing these to gain some more performance should not be done. \person{Kernighan} and \person{Pike} state clear: ``[T]he first principle of optimization is \emph{don't}.''\cite[page~165]{kernighan99}. \masqmail\ is not a program to be used on large servers, but on small devices. Thus important for \masqmail\ could be energy and heat saving, maybe also system resources, but not performance. Anyway, simplicity and clearness are of higher value.
meillo@196 288
meillo@225 289 Portability among the various flavors of \unix\ systems is a goal, because these systems are the ones \MTA{}s run on usually. Portability problems with non-\unix\ platforms are primary expected to come from file systems lacking required features. But no special care should be taken here.
meillo@196 290
meillo@219 291 Configuration could be eased more, by providing configuration generators to be able to use \masqmail\ right ``out of the box'' after running one of several configuration scripts for common setups. This would improve \masqmail's usability for not technical educated people.
meillo@196 292
meillo@196 293
meillo@196 294
meillo@200 295 \subsubsection*{The need for structural changes}
meillo@196 296
meillo@219 297 Adding authentication and encryption support, for example, is limited to a narrow region in the code. Such features are addable to the current code base without much problem. In contrast does adding support for new protocols or mail processing interfaces to external programs require a lot of effort. Changes in many parts of the source code are required. It is a bad idea to implement large retro-fitted features into software that is critical about security and reliability, like \MTA{}s. Worse if these features need changes in the program's structure, like adding mail scanning interfaces would do.
meillo@196 298
meillo@225 299 If such large features are needed, it is best to redesign the program's structure and rebuild it. A program's structure is primary its architecture. Which is the most influencing design decision, and has the greatest impact on the program's future capabilities. The architecture defines what the program can do, and how it can be used. If the architecture does not fit to the requirements, development will reach a dead end \dots\ further work then will make everything worse. The only good solution is to change the architecture, which, sadly but most likely, means a redesign from scratch.
meillo@196 300
meillo@225 301 Quality properties, like security and reliability, as well as extendability and maintainability, can hardly be added afterwards---if at all. Only structural changes will improve them. Hence, if security, reliability, extendability (to add support for future mail transfer protocols), or maintainability shall be improved, a redesign of \masqmail\ is the only sane way to go.
meillo@146 302
meillo@200 303 %\person{Hafiz} adds: ``The major idea is that security cannot be retrofitted into an architecture.''\cite[page 64]{hafiz05}
meillo@187 304
meillo@200 305
meillo@200 306
meillo@200 307
meillo@200 308 \section{Discussion on MTA architecture}
meillo@187 309
meillo@225 310 \masqmail's current architecture is monolithic like \sendmail's and \exim's. But more than the other two, is it one block of interweaved code. \exim\ has a highly structured code with many internal interfaces, a good example is the one for authentication ``modules''. %fixme: add ref
meillo@219 311 \sendmail\ provides now, with its \name{milter} interface, standardized connection channels to external modules.
meillo@188 312 \masqmail\ has none of them; it is what \sendmail\ was in the beginning: a single large block.
meillo@161 313
meillo@219 314 Figure \ref{fig:masqmail-arch} is a call graph generated from \masqmail's source code, excluding logging functions. It gives a impression of how interweaved the internals are.
meillo@219 315 %fixme: what is included, what not?
meillo@161 316
meillo@161 317 \begin{figure}
meillo@161 318 \begin{center}
meillo@219 319 \vspace*{2ex}
meillo@211 320 \includegraphics[scale=0.75]{img/callgraph.eps}
meillo@161 321 \end{center}
meillo@200 322 \caption{Call graph of \masqmail\ to show its internal structure}
meillo@161 323 \label{fig:masqmail-arch}
meillo@161 324 \end{figure}
meillo@161 325
meillo@225 326 \sendmail\ improved its old architecture by adding the milter interface, to include further functionality by invoking external programs. \exim\ was designed, and is carefully maintained, with a modular-like code structure in mind. \qmail\ started from scratch with a ``security-first'' approach, \postfix\ improved on it, and \name{sendmail X}/\name{MeTA1} tries to adopt the best of \qmail\ and \postfix\ to completely replace the old \sendmail\ architecture. \person{Hafiz} describes this evolution of \mta\ architecture very well \cite{hafiz05}.
meillo@161 327
meillo@225 328 Every one of these programs is more modular, or became more modular over time, than \masqmail\ is. Modern requirements like spam protection and future requirements like---probably---the use of new mail transport protocols demand for modular designs in order to keep the software simple. Simplicity is a key property for security. ``[T]he essence of security engineering is to build systems that are as simple as possible.''\cite[page 45]{graff03}
meillo@161 329
meillo@219 330 \person{Hafiz} agrees: ``The goal of making software secure can be better achieved by making the design simple and easier to understand and verify.'' \cite[page 64]{hafiz05}. He identifies the security of \qmail\ to come from it's \name{compartmentalization}, which goes hand in hand with modularity:
meillo@163 331 \begin{quote}
meillo@218 332 A perfect example is the contrast between the feature envy early \sendmail\ architecture implemented as one process and the simple, modular architecture of \qmail. The security of \qmail\ comes from its compartmentalized simple processes that perform one task only and are therefore testable for security.
meillo@218 333 \hfill\cite[page 64]{hafiz05}
meillo@163 334 \end{quote}
meillo@219 335 Equal does \person{Dent} see the situation for \postfix: ``The modular architecture of Postfix forms the basis for much of its security.'' \cite[page 7]{dent04}
meillo@200 336
meillo@200 337 Modularity is also needed to satisfy modern \MTA\ requirements, in providing a clear interface to add functionality without increasing the overall complexity much.
meillo@161 338
meillo@188 339 Security comes from good design, as \person{Graff} and \person{van Wyk} explain:
meillo@163 340 \begin{quote}
meillo@225 341 Good design is the sword and shield of the security-conscious developer. Sound design defends your application from subversion or misuse, protecting your network and the information on it from internal and external attacks alike. It also provides a safe foundation for future extensions and maintenance of the software.
meillo@163 342 %
meillo@163 343 %Bad design makes life easier for attackers and harder for the good guys, especially if it contributes to a false sends of security while obscuring pertinent failings.
meillo@218 344 \hfill\cite[page 55]{graff03}
meillo@163 345 \end{quote}
meillo@161 346
meillo@161 347
meillo@219 348 All this leads to the wish of a rewrite of \masqmail, using a modern, modular architecture, \emph{if} further features need to be added---features that require changes in \masqmail's structure. But a rewrite is also mandatory, if \masqmail\ should become a modern \MTA, with good quality properties.
meillo@161 349
meillo@225 350 But redesigning and rewriting a software from scratch is hard. It takes time to design a new architecture, which then must prove it is secure and reliable. As well is much time and work needed to implement the design, test it, fix bugs, and so on. If flaws in the design appear during prototype implementation, it is necessary to start again. Thus the gain of a new design must overweight the effort needed.
meillo@161 351
meillo@188 352 \person{Wheeler}'s program \name{sloccount} calculates following estimations for \masqmail's code base as of version 0.2.21 (excluding library code):
meillo@188 353 {\small
meillo@188 354 \begin{verbatim}
meillo@188 355 Total Physical Source Lines of Code (SLOC) = 9,041
meillo@188 356 Development Effort Estimate, Person-Years (Person-Months) = 2.02 (24.22)
meillo@188 357 (Basic COCOMO model, Person-Months = 2.4 * (KSLOC**1.05))
meillo@188 358 Schedule Estimate, Years (Months) = 0.70 (8.39)
meillo@188 359 (Basic COCOMO model, Months = 2.5 * (person-months**0.38))
meillo@188 360 Estimated Average Number of Developers (Effort/Schedule) = 2.89
meillo@188 361 Total Estimated Cost to Develop = $ 272,690
meillo@188 362 (average salary = $56,286/year, overhead = 2.40).
meillo@188 363 SLOCCount, Copyright (C) 2001-2004 David A. Wheeler
meillo@188 364 \end{verbatim}
meillo@188 365 }
meillo@219 366 The development cost is not relevant for a \freesw\ project with volunteer developers, but the development time is. About 24 man-months are estimated. The current code base was written almost completely by Oliver \person{Kurth} within four years, in his spare time. This means he needed around twice as much time. Of course, he programmed as volunteer developer, not as employee with eight work-hours per day.
meillo@161 367
meillo@225 368 Given the assumptions that (1) an equal amount of code needs to be produced for a new \masqmail, (2) a third of existing code can be reused plus concepts and knowledge, and (3) development speed is like \person{Kurth}'s. Then it would take between two and three years to have a redesigned new \masqmail\ with the same features that \masqmail\ now has. Less time would be needed if a simpler architecture allows faster development, better testing, and less bugs.
meillo@200 369
meillo@177 370
meillo@177 371
meillo@177 372
meillo@177 373
meillo@196 374
meillo@196 375
meillo@196 376
meillo@196 377
meillo@196 378
meillo@196 379 \section{Result}
meillo@196 380
meillo@219 381 The most needed features---authentication and encryption---can be added to the current code base with changes in only few parts of the source. These changes should be made soon. Archiving of mail is another feature to add then. More complete logging coverage, reporting of unsafe environment, and fixing high risk security flaws are quality improvements to do. All this work should be done on basis of the current code.
meillo@196 382
meillo@219 383 All other work depends on how the plans for \masqmail's future look like.
meillo@196 384
meillo@219 385 What shall \masqmail\ be like, in, for instance, five years?
meillo@196 386
meillo@219 387 Two ways of further development come to mind.
meillo@196 388
meillo@225 389 First, stick to the old architecture and try to add features as possible. This approach needs less effort to be spent, because a working code is already present. Further development is only adding small increments to a exiting code base. But the further development goes, the larger is the work needed to add more functionality, and the more bugs will appear, caused by the increasing complexity. Quality of the software will decrease, because lacking of clear internal structure encourages further work to be quick fixes rather than good solutions.
meillo@196 390
meillo@225 391 Second, the way of designing \masqmail\ from scratch and rebuilding it. A lot of time and work is required to do this. Additionally, a new design from scratch introduces new risks: Is the design really better? Was thought of everything? Will there come problems not foreseeable now? Starting from scratch also means a step back. Against these disadvantages stands the gain from the new design: Further development will be easier and probably faster, overall quality will be better and easier to keep up, and dead ends for further development are better avoidable.
meillo@196 392
meillo@219 393 Essentially, the decision for one of the ways depends on the question whether \masqmail\ should remain what it is, then the first option seems to be the right one to choose. Or whether \masqmail\ should become a modern \mta\ which is able to expand to include new functionality, then the second option is to choose.
meillo@196 394
meillo@219 395 Security, extendability, and the other quality properties appear to have also crucial importance in this decision. If they are required for future versions of \masqmail, then a new design is a must.
meillo@196 396
meillo@225 397 \person{Graff} and \person{van Wyk} describe the situation well: ``[I]n today's world, your software is likely to have to operate in a very hostile security environment.'' \cite{graff03}. An old-fashioned \mta\ depends, for sure, on a dieing branch, called \name{trusted environments}. And nothing other than a fresh and better design will help to survive.
meillo@196 398
meillo@219 399 The suggested further development plan for \masqmail\ is:
meillo@219 400 \begin{enumerate}
meillo@225 401 \item The short time goal: Add the most needed features, being authentication and encryption, to the current code base. \item The long time goal: Design a new architecture that satisfies the requirements identified, especially the quality requirements. The implementation of this design shall then, after being usable and throughout tested, supersede the old \masqmail.
meillo@219 402 \end{enumerate}
meillo@196 403
meillo@219 404 This plan is similar to the change from \sendmail\ to \name{sendmail X}/\name{MeTA1}, except the \sendmail\ change was much too late.
meillo@196 405
meillo@219 406 The following chapter is about the work on the current code base, to reach the short time goals. The chapter afterwards then introduces a new, modern design for future versions of \masqmail.
meillo@196 407
meillo@219 408
meillo@219 409 %The plan is to first do the most needed stuff on the old design to make it still usable; then design a new version from scratch, for the future.