docs/diploma

annotate thesis/tex/1-Introduction.tex @ 371:44a3188bf6d2

find changesets by author, revision, files, or words in the commit message
removed automated index generation; new aliases
author meillo@marmaro.de
date Sat, 31 Jan 2009 19:25:25 +0100
parents 63fb9fba6c77
children d51894e48762
rev   line source
meillo@26 1 \chapter{Introduction}
meillo@42 2 \label{chap:introduction}
meillo@26 3
meillo@370 4 This chapter introduces some basic email concepts that are essential for understanding the remainder of the thesis. Then \masqmail---the program of interest---is presented. History, typical usage, and the function it provides are described. After an explanation of \masqmail's relevance, its weaknesses are pointed out. Solving these weaknesses is the topics that is covered throughout this thesis.
meillo@92 5
meillo@92 6
meillo@229 7
meillo@229 8
meillo@245 9
meillo@245 10 \section{Email prerequisites}
meillo@245 11
meillo@366 12 Electronic mail is a service on the Internet and thus, like other Internet services, defined and standardized by \RFC{}s under management of the \name{Internet Engineering Task Force} (short: \NAME{IETF}). \RFC{}s are highly technical documents and it is not required that the readers of this thesis are familiar with them.
meillo@306 13
meillo@370 14 This section gives an introduction into the basic internals of the email system in a low-technical language. It is intended to make the reader familiar with the essential concepts of email as they are essential throughout the thesis.
meillo@245 15
meillo@245 16
meillo@245 17 \subsubsection{Mail agents}
meillo@245 18
meillo@370 19 This thesis will frequently use the three terms: \MTA, \NAME{MUA}, and \NAME{MDA}, naming the three different kinds of nodes of the email infrastructure. Here, they are explained with references to the ``snail mail'' system which is known from everyday life. Figure \ref{fig:mail-agents} shows the relation between those three mail agents and the way an email message takes when passing through the system.
meillo@253 20
meillo@269 21 \begin{description}
meillo@269 22 \item[\MTA:]
meillo@370 23 \name{Mail Transfer Agents} are the post offices for electronic mail. The basic job of an \MTA\ is to transport mail from senders to recipients, or more pedantic: from \MTA\ to \MTA. \sendmail, \exim, \qmail, \postfix, and, of course, \masqmail\ are \MTA{}s. \MTA{}s are explained in more detail in chapter \ref{chap:mail-transfer-agents}.
meillo@245 24
meillo@269 25 \item[\NAME{MUA}:]
meillo@370 26 \name{Mail User Agents} are the software users deal with. A user writes and reads email with it. The \NAME{MUA} passes outgoing mail to the nearest \MTA. Also the \NAME{MUA} displays the contents of the user's mailbox. Well known \NAME{MUA}s are \name{Mozilla Thunderbird} and \name{mutt} on \unix\ systems, and \name{Microsoft Outlook} on \name{Windows}.
meillo@245 27
meillo@269 28 \item[\NAME{MDA}:]
meillo@366 29 \name{Mail Delivery Agents} correspond to postmen in the real world. They receive mail, destined to recipients they are responsible for, from an \MTA, and deliver it to the mailboxes of those recipients. Many \MTA{}s include an own \NAME{MDA}, but independent ones exist: \name{procmail} and \name{maildrop} are examples.
meillo@269 30 \end{description}
meillo@245 31
meillo@253 32 \begin{figure}
meillo@253 33 \begin{center}
meillo@253 34 \includegraphics[scale=0.75]{img/mail-agents.eps}
meillo@253 35 \end{center}
meillo@253 36 \caption{Mail agents and the way a mail message takes}
meillo@253 37 \label{fig:mail-agents}
meillo@253 38 \end{figure}
meillo@245 39
meillo@229 40
meillo@253 41
meillo@229 42
meillo@229 43
meillo@229 44
meillo@245 45 \subsubsection{Mail transfer with SMTP}
meillo@245 46
meillo@366 47 Today most of the email is transferred using the \name{Simple Mail Transfer Protocol} (short: \SMTP), which is defined in \RFC\,821 and the successors \RFC\,2821 and \RFC\,5321. A good entry point for further information is \citeweb{wikipedia:smtp}.
meillo@245 48
meillo@245 49 A selection of important concepts of \SMTP\ is explained here.
meillo@245 50
meillo@253 51 First the \name{store and forward} transfer concept. This means mail messages are sent from \MTA\ to \MTA, until the final \MTA\ (the one which is responsible for the recipient) is reached. The message is gets stored for some time on each \MTA, until it is forwarded to the next \MTA.
meillo@245 52
meillo@366 53 This leads to the concept of \name{responsibility}. A mail message is always in the responsibility of one system. First it is the \NAME{MUA}. When it is transferred to an \MTA, this \MTA\ takes over the responsibility for the message too. The \NAME{MUA} can then delete its copy of the message. This is the same for each transfer---from \MTA\ to \MTA\ and finally from \MTA\ to the \NAME{MDA}---the message gets transferred and if the transfer was successful, the responsibility for the message is transferred as well. The responsibility chain ends at a user's mailbox where he himself has control on the message.
meillo@245 54
meillo@366 55 A third concept is about failure handling. At any step on the way an \MTA\ may receive a message it is unable to handle. In such a case this receiving \MTA\ will \name{reject} the message before it takes responsibility for it. The sending \MTA\ still has responsibility for the message and may try other ways for sending the message. If none succeeds the \MTA\ will send a \name{bounce message} back to the original sender with information on the type of failure. Bounces are only sent if the failure is expected to be permanent or if the transfer still was unsuccessful after many tries.
meillo@245 56
meillo@245 57
meillo@245 58
meillo@245 59 \subsubsection{Mail messages}
meillo@245 60
meillo@366 61 Mail messages consist of text in a specific format. This format is specified in \RFC\,822, and the successors \RFC\,2822 and \RFC\,5322.
meillo@245 62
meillo@366 63 A message has two parts, the \name{header} and the \name{body}. The header of an email message is similar to the header of a (formal) letter. It spans the first lines of the message up to the first empty line. The header consists of several lines, called \name{header lines} or simply \name{headers}. They specify the sender, the recipient(s), the date, and possibly further information. Their order is irrelevant. Headers are named like the colon-separated start of those lines, for example the ``\texttt{Date:}'' header. A user may write the header himself but normally the \NAME{MUA} does this job.
meillo@245 64
meillo@316 65 The body is the payload of the message. It is under full control of the user. From the view point of the \SMTP\ protocol, it must consist of only 7-bit \NAME{ASCII} text. But arbitrary content can be included by encoding it to 7-bit \NAME{ASCII}. \NAME{MIME} is the common \SMTP\ extension to handle such conversion automatically in \NAME{MUA}s.
meillo@245 66
meillo@253 67 Following is a sample mail message with four header lines (\texttt{From:}, \texttt{To:}, \texttt{Date:}, and \texttt{Subject:}) and three lines of message body.
meillo@245 68
meillo@269 69 \codeinput{input/sample-email.txt}
meillo@245 70
meillo@366 71 Email messages are put into \name{envelopes} for transfer. This concept is also derived from the real world so it is easy to understand. The envelope is used to route the message from sender to recipient. It contains the sender's address and addresses of one or more recipients. Envelopes are generated by \MTA{}s, usually from mail header data. The user has not to deal with them.
meillo@253 72
meillo@260 73 Each \MTA\ on the way reads envelopes it receives and generates new ones. If a message has recipients on different hosts, then the message gets copied and sent within multiple envelopes, one for each host.
meillo@260 74
meillo@260 75 The sample message would would lead to two envelopes, one from \name{markus@host01} to \name{alice@host02}, the other from \name{markus@host01} to \name{bob@host03}. Both envelopes would contain the same message.
meillo@245 76
meillo@245 77
meillo@245 78
meillo@245 79
meillo@229 80
meillo@229 81
meillo@92 82 \section{The \masqmail\ project}
meillo@102 83 \label{sec:masqmail}
meillo@96 84
meillo@370 85 The \masqmail\ project was initiated by \person{Oliver Kurth} in 1999. His aim was to create a small \MTA\ that is especially focused on computers with dial-up Internet connections. Throughout the next four years he worked steadily on it, releasing new versions every few weeks. During the active phase of development 53 version have been released. In average, this is a new version every 20 days.
meillo@96 86
meillo@370 87 This thesis is based on the latest release of \masqmail---version 0.2.21, dated November 2005. It was released after a 28 month gap of inactivity. The source code of 0.2.21 is the same as of 0.2.20, with only build documents modified. The homepage of \masqmail\ \citeweb{masqmail:homepage2} does not include this latest release, but it can be retrieved from the \debian\ package pool\footnote{The \NAME{URL} is:\\\url{http://ftp.de.debian.org/debian/pool/main/m/masqmail/masqmail_0.2.21.orig.tar.gz}} \citeweb{packages.debian}.
meillo@96 88
meillo@370 89 \masqmail\ is covered by the \name{General Public License} (short: \NAME{GPL}) \cite{fsf:gpl} which qualifies it as Free Software \cite{fsf:freesw-definition}.
meillo@102 90
meillo@370 91 \person{Kurth} abandoned \masqmail\ after 2005 and no one adopted the project since then. Thus, the author of this thesis decided to take over responsibility for \masqmail\ now. He received \person{Kurth}'s permission to do so in private telephone conversation with \person{Kurth} on September 4, 2008.
meillo@102 92
meillo@370 93 The program's new homepage \citeweb{masqmail:homepage} includes a collection of available information about this \MTA.
meillo@102 94
meillo@102 95
meillo@96 96
meillo@92 97
meillo@366 98 \subsection{Target field}
meillo@266 99 \label{sec:masqmail-target-field}
meillo@245 100
meillo@370 101 \person{Kurth}'s intention when creating \masqmail\ is best told in his own words:
meillo@92 102 \begin{quote}
meillo@366 103 MasqMail is a mail server designed for hosts that do not have a permanent internet connection eg. a home network or a single host at home. It has special support for connections to different \NAME{ISP}s. It replaces sendmail or other \MTA{}s such as qmail or exim.
meillo@257 104 \hfill\citeweb{masqmail:homepage2}
meillo@257 105 \end{quote}
meillo@366 106 It is intended to cover a specific niche: non-permanent Internet connection and different \name{Internet Service Providers} (short: \NAME{ISP}s).
meillo@257 107
meillo@366 108 Although it can basically replace other \MTA{}s it is not \emph{generally} aimed to do so. The package description of \masqmail\ within \debian\ states this more clearly by changing the last sentence to:
meillo@257 109 \begin{quote}
meillo@366 110 In these cases, MasqMail is a slim replacement for full-blown \MTA{}s such as sendmail, exim, qmail or postfix.
meillo@257 111 \hfill\citeweb{packages.debian:masqmail}
meillo@257 112 \end{quote}
meillo@316 113 The program is a good replacement ``in these cases'', but not generally, since is lacks essential features for running on mail servers. It is primarily not secure enough for being accessible from untrusted locations.
meillo@257 114
meillo@316 115 \masqmail\ is best used in home networks, which are non-permanently connected to the Internet. It is easy configurable for situations which are rarely solvable with the common \MTA{}s. Such include different handling of mail to local or remote destination and respecting different routes of being online connection. These features are explained in more detail in the following \name{Features} section on page \ref{sec:masqmail-features}. %fixme: is it still called ``features''?
meillo@257 116
meillo@257 117 While many other \MTA{}s are general purpose \MTA{}s, \masqmail\ aims on special situations. Nevertheless, it can be used as general purpose \MTA, too. Especially this was a design goal of \masqmail: To be a replacement for \sendmail, or similar well known \MTA{}s.
meillo@257 118
meillo@370 119 \masqmail\ is designed to run on workstations and on servers in small networks, like they are common in \NAME{SOHO}s (\name{Small Offices/Home Offices}).
meillo@257 120
meillo@257 121
meillo@257 122
meillo@260 123 \subsubsection*{Typical usage scenarios}
meillo@257 124
meillo@316 125 This section describes three common setups that makes sensible use of \masqmail. The first two are shown in figure \ref{fig:masqmail-typical-usage}.
meillo@257 126
meillo@257 127 \begin{figure}
meillo@257 128 \begin{center}
meillo@257 129 \includegraphics[scale=0.75]{img/masqmail-typical-usage.eps}
meillo@257 130 \end{center}
meillo@257 131 \caption{Typical usage scenarios for \masqmail}
meillo@257 132 \label{fig:masqmail-typical-usage}
meillo@257 133 \end{figure}
meillo@257 134
meillo@269 135 Imagine a home network consisting of some workstations which is connected to the Internet.
meillo@260 136
meillo@269 137 \begin{description}
meillo@269 138 \item[Scenario 1:]
meillo@369 139 \label{scenario1}
meillo@316 140 If no server is present, every workstation would be equipped with \masqmail. Mail transfer within the same machine or within the local net works straight forward using direct transfer. Outgoing mail to the Internet is sent, to an \name{Internet Service Provider} (short: \NAME{ISP}) for relaying whenever the router goes online. The configuration of \masqmail\ would be the same on every computer, except different host names.
meillo@269 141 To receive mail from the Internet requires a mailbox on the \NAME{ISP}'s mail server. Mail needs to be fetched from the \NAME{ISP}'s server onto the workstation using the \NAME{POP3} or \NAME{IMAP} protocol.
meillo@269 142
meillo@269 143 \item[Scenario 2:]
meillo@369 144 \label{scenario2}
meillo@369 145 In the same network but with a server, one could have \masqmail\ running on the server and using simple forwarders (see \ref{subsec:relay-only}) on the workstations to transfer mail to the server. The server would then, dependent on the destination of the message, deliver locally or relay to an \NAME{ISP}'s server for further relay. This setup does only support mail transfer to the server but not back to a workstation. However, this can be solved by mounting the user's mailbox from the server to the workstation or by using \NAME{POP3} or \NAME{IMAP}. Mail transfer from the \NAME{ISP} to the local server needs \NAME{POP3} or \NAME{IMAP} as well.
meillo@269 146
meillo@269 147 \item[Scenario 3:]
meillo@369 148 \label{scenario3}
meillo@369 149 A third scenario is unrelated as it is about notebooks. Notebooks are usually used as mobile workstations. One uses them to work at different locations. With the increasing popularity of wireless networks this becomes more and more common. Different networks demand for different setups: In one network it is best to send mail to an \NAME{ISP} for relay. In another network it might be preferred to use a local mail server. A third network may have no Internet access at all, hence using a local mail server is required. All these different setups can be configured once and then used by simply telling the online state to \masqmail, even automatically within a network setup script.
meillo@269 150 \end{description}
meillo@269 151
meillo@269 152
meillo@369 153 In general, all kinds of usage scenarios within a trusted network are possible. Important to notice is that mail can not be send from outside into the trusted network then. For using \masqmail\ on notebooks it is suggested to only accept mail from local users because notebooks are often in untrusted environments.
meillo@257 154
meillo@257 155
meillo@257 156
meillo@257 157
meillo@257 158 \subsubsection*{Limitations}
meillo@257 159
meillo@369 160 Although \masqmail\ is seen as a replacement for other general purpose \MTA{}s, it should not be used on large mail servers. The reasons are that it implements only a basic subset of features and that its performance and security is not as good as needed for such usage.
meillo@257 161
meillo@369 162 The author, \person{Kurth}, warns on the old project's website about using \masqmail\ to accept connections from the Internet because of the risk of being an open relay:
meillo@257 163
meillo@257 164 \begin{quote}
meillo@257 165 MasqMail is not designed to run on a host with a permanent internet connection. It does not have the ability to check for spam mail and it will relay everything from everywhere to everywhere. Use another mail server such as exim for permanent connections.
meillo@257 166 \hfill\citeweb{masqmail:homepage2}
meillo@92 167 \end{quote}
meillo@92 168
meillo@369 169 The actual problem is not the permanent Internet connection but listening for incoming mail on it. If a firewall is closed for incoming mail, then the permanent Internet connection is no problem. To use \masqmail\ for permanent Internet connections it needs to be secured with care.
meillo@160 170
meillo@369 171 The Internet is the common example for an untrusted network but other networks may be untrusted too.
meillo@160 172
meillo@160 173
meillo@160 174
meillo@245 175
meillo@245 176
meillo@245 177
meillo@245 178
meillo@245 179
meillo@245 180
meillo@245 181
meillo@245 182
meillo@245 183
meillo@245 184 \subsection{Features}
meillo@238 185
meillo@369 186 Here regarded is version 0.2.21 of \masqmail. This is the last version released by \person{Oliver Kurth}.
meillo@238 187
meillo@238 188
meillo@238 189 \subsubsection*{The source code}
meillo@238 190
meillo@369 191 \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 which contain about 9\,000 lines of code\footnote{Measured with \name{sloccount} by David A.\ Wheeler \citeweb{sloccount}.}. 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@238 192
meillo@238 193 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@238 194
meillo@369 195 Some parts of \masqmail's functionality can be included or excluded at compile time by defining symbols. To enable maildir support for example, one has to add \verb_--enable-maildir_ to the configure call. Otherwise the concerning code gets removed during preprocessing.
meillo@260 196
meillo@369 197 With \masqmail\ comes the small tool \path{mservdetect}; it helps setting up a configuration that uses the \name{mserver} system for online state detection. Two other binaries get compiled for testing purposes: \path{readtest} and \path{smtpsend}. These three additional programs use parts of \masqmail's source code; they only add a file with a \verb+main()+ function each.
meillo@238 198
meillo@238 199
meillo@238 200
meillo@238 201 \subsubsection*{Features}
meillo@238 202 \label{sec:masqmail-features}
meillo@238 203
meillo@369 204 \masqmail\ supports two channels for incoming mail:
meillo@369 205
meillo@369 206 \begin{enumerate}
meillo@369 207 \item Standard input which is used when \path{masqmail} (or the \path{sendmail} link) is executed on the command line
meillo@369 208 \item A \NAME{TCP} socket which is used by local or remote clients that talk \SMTP
meillo@369 209 \end{enumerate}
meillo@369 210
meillo@369 211 The outgoing channels for mail are:
meillo@369 212
meillo@369 213 \begin{enumerate}
meillo@369 214 \item Direct delivery to local mailboxes (in \name{mbox} or \name{maildir} format)
meillo@369 215 \item Local pipes to pass mail to a program (e.g.\ to \NAME{MDA}s or to gateways to \NAME{UUCP} or fax)
meillo@369 216 \item \NAME{TCP} sockets to transfer mail to other \MTA{}s using the \SMTP\ protocol
meillo@369 217 \end{enumerate}
meillo@369 218
meillo@369 219 Figure \ref{fig:masqmail-channels} shows this as a picture. (The ``online state'' input is explained a bit later.)
meillo@260 220
meillo@260 221 \begin{figure}
meillo@260 222 \begin{center}
meillo@260 223 \includegraphics[scale=0.75]{img/masqmail-channels.eps}
meillo@260 224 \end{center}
meillo@260 225 \caption{Incoming and outgoing channels of \masqmail}
meillo@260 226 \label{fig:masqmail-channels}
meillo@260 227 \end{figure}
meillo@238 228
meillo@369 229 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 gateway application like \name{openssl}.
meillo@238 230
meillo@369 231 Mail queuing is essential for \masqmail\ and thus supported of course, alias expansion is also supported.
meillo@238 232
meillo@370 233 The \masqmail\ executable can be called by various names for sendmail-compatibility reasons. As many programs expect the \MTA\ to be located at \path{/usr/lib/sendmail} or \path{/usr/sbin/sendmail}, symbolic links are pointing from there to the \masqmail\ executable. Further more does \sendmail\ supports calling it with a different name instead of supplying command line arguments. The best known of these shortcuts is \path{mailq} which is equivalent to calling it with the argument \verb+-bq+. \masqmail\ recognizes the shortcuts \path{mailq}, \path{smtpd}, \path{mailrm}, \path{runq}, \path{rmail}, and \path{in.smtpd}. The first two are inspired by \sendmail. Not implemented yet is the shortcut \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 strict requirements.} \path{hoststat} and \path{purgestat} are missing for complete sendmail-compatibility.
meillo@238 234 %masqmail: mailq, mailrm, runq, rmail, smtpd/in.smtpd
meillo@238 235 %sendmail: hoststat, mailq, newaliases, purgestat, smtpd
meillo@238 236
meillo@370 237 Additional to the \mta\ job, \masqmail\ also offers mail retrieval services by acting as a \NAME{POP3} client. It can fetch mail from different remote locations, also dependent on the active online connection. Such functionality is especially useful in a setup like \name{Scenario 2} on page \pageref{scenario2}.
meillo@238 238
meillo@238 239
meillo@238 240
meillo@370 241 \subsubsection*{Online detection and online routes}
meillo@245 242 \label{sec:masqmail-routes}
meillo@238 243
meillo@275 244 \masqmail\ focuses on handling different 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 to determine if some message is allowed to be sent over it. Mail to destinations outside the local network gets queued until a suitable online connections is available.
meillo@260 245
meillo@370 246 The idea behind this concept is sending mail to the Internet through the mail server of the same \NAME{ISP} over which one had dialed in. It was quite common that \NAME{ISP}s accepted mail for relay only if it came from a online connection they managed. This means, it was not possible to relay mail through the mail server of one \NAME{ISP} while being online through the connection of another \NAME{ISP}. \masqmail\ is a solution to the wish of switching the relaying mail server easily.
meillo@257 247
meillo@316 248 Related is \masqmail's ability to rewrite the sender's email address dependent on which \NAME{ISP} is used. This prevents mail from being likely classified as spam.
meillo@257 249
meillo@369 250 To react on the different situations, \masqmail\ needs to query the current online state. Is an online connection available? And if it is: Which one? Three methods are implemented:
meillo@238 251
meillo@369 252 \begin{enumerate}
meillo@369 253 \item Reading from a file
meillo@369 254 \item Reading the output of a command
meillo@369 255 \item Querying an \name{mserver} system
meillo@369 256 \end{enumerate}
meillo@238 257
meillo@369 258 Each method may return a string naming the routes that is online or returning nothing to indicate offline state.
meillo@369 259
meillo@369 260
meillo@369 261 Mail for hosts inside the local network or for users on the local machine is not touched by this concept; such mail is always sent immediately.
meillo@238 262
meillo@238 263
meillo@238 264
meillo@238 265
meillo@245 266
meillo@245 267
meillo@245 268
meillo@245 269
meillo@370 270 \section{Why \masqmail\ is worth it}
meillo@245 271
meillo@369 272 First of all, \masqmail\ is better suited for its target field of operation (multiple non-permanent online connections) than every other \MTA. Especially is such usage easy to set up because \masqmail\ was designed for that. Many alternative \MTA{}s were not designed for those scenarios at all as the following two example show: ``Exim is designed for use on a network where most messages can be delivered at the first attempt.'' \cite[page~30]{hazel01}. ``qmail was designed for well-connected hosts: those with high-speed, always-on network connectivity.'' \cite[page9]{sill02}.
meillo@369 273
meillo@369 274 %fixme: hikernet
meillo@245 275
meillo@316 276 Additionally does \masqmail\ make it easy to run an \MTA\ on workstations or notebooks. There is no need to do complex configuration or to be a mail server expert. Only a handful of options need to be set; the host name, the local networks, and one route for relaying are sufficient in most times. %fixme: is that true?
meillo@245 277
meillo@369 278 Probably users say it best; in this case \person{Derek Broughton}:
meillo@284 279 \begin{quote}
meillo@284 280 No kidding. The whole point is that you \_have\_ to have an \MTA\ and you don't
meillo@284 281 want to configure Postfix/Exim/Sendmail/Qmail (almost all of which I've
meillo@284 282 actually done).
meillo@284 283
meillo@369 284 I now use masqmail -- it's really simple, my configuration is all in debconf,
meillo@284 285 it's supported by whereami, and it's really simple :-)
meillo@284 286
meillo@284 287 I'm sure you can make any \MTA\ behave nicely when offline, but it was a chore
meillo@284 288 with all of them.
meillo@284 289 \hfill\citeweb[post~\#8]{ubuntuforums:simple-mailer}
meillo@284 290 \end{quote}
meillo@284 291
meillo@370 292 Not to forget \masqmail's size. \masqmail\ is much smaller than full-blown \MTA{}s like \sendmail, \postfix, or \exim, and still smaller than \qmail. (See section \ref{sec:mta-comparison} for details.) This makes \masqmail\ a good choice for workstations or even embedded computers.
meillo@245 293
meillo@284 294 Again words of a user who chose \masqmail\ as \MTA\ on his old laptop with a 75 megahertz processor and eight megabytes of \NAME{RAM}:
meillo@284 295 \begin{quote}
meillo@284 296 Masqmail appears to be a great sendmail replacement in this case. It's small and is built to support sending mail ``off-line'', and to connecting to the \SMTP\ servers of several \NAME{ISP}s.
meillo@284 297 \hfill\citeweb{stosberg:low-mem-laptop}
meillo@284 298 \end{quote}
meillo@92 299
meillo@92 300
meillo@92 301
meillo@370 302 Although the development on \masqmail\ has been stopped in 2003, \masqmail\ still has its users. Having users is already reason enough for further development and maintenance. This applies especially when the software covers a niche and when requirements for such software in general changed. Both is the case for \masqmail.
meillo@284 303
meillo@369 304 It is difficult to get numbers about users of Free Software because no one needs to tell anyone when he uses some software. \debian's \name{popcon} statistics \citeweb{popcon.debian} are a try to provided numbers. For January 2009, the statistics report 60 \masqmail\ installations of which 49 are in active use. If it is assumed that one third of all \debian\ users report their installed software\footnote{One third is a high guess as it means there would be only about 230 thousand \debian\ installations in total. But according to the \name{Linux Counter} \citeweb{counter.li.org} between 490 thousand and 12 million \debian\ users can be estimated.}, there would be in total around 150 active \masqmail\ installations in \debian. \name{Ubuntu} which also does \name{popcon} statistics \citeweb{popcon.ubuntu}, counts 82 installations with 13 active ones. If here also one third of all systems submit their data, 40 active installations can be added. Including a guessed amount of additional 30 installations on other \unix\ operating systems makes about 220 \masqmail\ installations in total. Of course one person may have \masqmail\ installed on more than one computer, but a total of 150 different users seems to be realistic.
meillo@284 305
meillo@286 306 %The increasing number of systems using \masqmail, as it is shown on the \name{popcon} graph \citeweb{popcon.debian:masqmail}, seems to be impressive in the beginning as \masqmail\ was not developed during that time. But it might come from the increasing popularity of \name{popcon} over the time.
meillo@284 307
meillo@369 308 One thing became clear now: \masqmail\ has users. And software that is used should be developed and maintained.
meillo@92 309
meillo@92 310
meillo@275 311 % alternative: http://anfi.homeunix.org/sendmail/dialup10.html
meillo@96 312
meillo@275 313
meillo@175 314
meillo@96 315
meillo@96 316
meillo@245 317
meillo@245 318
meillo@245 319
meillo@245 320
meillo@92 321 \section{Problems to solve}
meillo@92 322
meillo@370 323 A program that is neglected for more than five years in a field of operation that changed during this time surely needs improvement. Security and spam have highly increased in importance since 2003. Dial-up connections became rare, instead broadband flat rates are common now. Other \MTA{}s evolved in respect to theses changes---\masqmail\ did not.
meillo@96 324
meillo@369 325 The current market situation and trends for the future need to be identified. Looks at other \MTA{}s need to be taken. Required work on \masqmail\ needs to be defined in combination with the evaluation of strategies to do this work. And a plan for further development should be created.
meillo@96 326
meillo@96 327
meillo@245 328
meillo@245 329
meillo@245 330
meillo@245 331 \section{Delimitation}
meillo@96 332
meillo@369 333 This thesis is neither a installation guide for \masqmail\ nor a detailed explanation of \masqmail's source code. Installation and setup guides can be found on \masqmail's homepage \citeweb{masqmail:homepage}.
meillo@96 334
meillo@369 335 The \NAME{POP3} functionality of \masqmail\ receives few regard in this document because it is not directly related to the core of \masqmail\ which is being an \MTA.
meillo@96 336
meillo@369 337 The \name{mserver} system to query the online state is also only mentioned but not regarded further. It seems best to move this functionality into a separate program which is run through the shell command interface, anyway.
meillo@96 338
meillo@150 339
meillo@369 340