1 \chapter{Introduction}

2 \label{chap:introduction}

3

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.

5

6

7

8

9

10 \section{Email prerequisites}

11

12 Electronic mail is a service on the Internet and thus, like other Internet services, defined and standardized by \name{Requests For Comments} (short: \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.

13 \index{ietf}

14 \index{rfc}

15

16 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.

17

18

19 \subsubsection{Mail agents}

20 \index{mail agents}

21

22 This thesis will frequently use the three terms: \MTA, \MUA{}, and \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.

23

24 \begin{description}

25 \item[\MTA:]

26 \index{mta}

27 \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}.

28

29 \item[\MUA{}:]

30 \index{mua}

31 \name{Mail User Agents} are the software users deal with. A user writes and reads email with it. The \MUA{} passes outgoing mail to the nearest \MTA. Also the \MUA{} displays the contents of the user's mailbox. Well known \MUA{}s are \name{Mozilla Thunderbird} and \name{mutt} on Unix systems, and \name{Microsoft Outlook} on \name{Windows}.

32

33 \item[\MDA{}:]

34 \index{mda}

35 \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 \MDA{}, but independent ones exist: \name{procmail} and \name{maildrop} are examples.

36 \end{description}

37 \index{procmail}

38

39 \begin{figure}

40 \begin{center}

41 \includegraphics[scale=0.75]{fig/mail-agents.eps}

42 \end{center}

43 \caption{Mail agents and the way a mail message takes}

44 \label{fig:mail-agents}

45 \end{figure}

46

47

48

49

50

51

52 \subsubsection{Mail transfer with SMTP}

53 \label{smtp-intro}

54

55 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}.

56 \index{smtp}

57 \index{rfc}

58

59 A selection of important concepts of \SMTP\ is explained here.

60 \index{smtp!concepts of}

61

62 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 stored for some time on each \MTA, until it is forwarded to the next \MTA.

63 \index{smtp!store-and-forward}

64

65 This leads to the concept of \name{responsibility}. A mail message is always in the responsibility of one system. First it is the \MUA. When it is transferred to an \MTA, this \MTA\ takes over the responsibility for the message, too. The \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 \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.

66 \index{mua}

67 \index{mda}

68 \index{smtp!responsibility}

69

70 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.

71 \index{smtp!bouncing}

72 \index{smtp!rejecting}

73

74

75

76 \subsubsection{Mail messages}

77

78 Mail messages consist of text in a specific format. This format is specified in \RFC\,822, and the successors \RFC\,2822 and \RFC\,5322.

79 \index{mail message}

80 \index{rfc}

81

82 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 \MUA{} does this job.

83

84 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 \MUA{}s.

85 \index{mua}

86 \index{mime}

87 \index{ascii}

88

89 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.

90

91 \codeinput{input/sample-email.txt}

92

93 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.

94

95 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.

96

97 The sample message 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.

98

99

100

101

102

103

104 \section{The \masqmail\ project}

105 \label{sec:masqmail}

106

107 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.

108 \index{masqmail}

109 \index{dial-up}

110

111 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 \name{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}.

112 \index{debian!package pool}

113

114 \masqmail\ is covered by the \name{General Public License} (short: \NAME{GPL}) version two or any later version \cite{fsf:gpl}. This qualifies \masqmail\ as Free Software \cite{fsf:freesw-definition}.

115 \index{gpl}

116 \index{Free Software}

117

118 \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.

119

120 The program's new homepage \citeweb{masqmail:homepage} includes a collection of available information about this \MTA.

121

122

123

124

125 \subsection{Target field}

126 \label{sec:masqmail-target-field}

127

128 \person{Kurth}'s intention when creating \masqmail\ is best told in his own words:

129 \index{masqmail}

130

131 \begin{quote}

132 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.

133 \hfill\citeweb{masqmail:homepage2}

134 \end{quote}

135

136 It is intended to cover a specific niche: non-permanent Internet connection and different \name{Internet Service Providers} (short: \NAME{ISP}s).

137

138 Although it can basically replace other \MTA{}s it is not \emph{generally} aimed to do so. The package description of \masqmail\ within \name{Debian} states this more clearly by changing the last sentence to:

139 \index{debian!masqmail package}

140

141 \begin{quote}

142 In these cases, MasqMail is a slim replacement for full-blown \MTA{}s such as sendmail, exim, qmail or postfix.

143 \hfill\citeweb{packages.debian:masqmail}

144 \end{quote}

145

146 The program is a good replacement ``in these cases'' but not generally, since it lacks essential features for running on publically accessable mail servers. It is primarily not secure enough for being accessible from untrusted locations.

147

148 \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 online connection. These features are explained in more detail in section~\ref{sec:masqmail-features}.

149 \index{non-permanent online connection}

150

151 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 \MTA{}s.

152 \index{masqmail}

153 \index{sendmail}

154

155 \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}).

156

157

158

159 \subsubsection*{Typical usage scenarios}

160

161 This section describes three common setups that make sensible use of \masqmail. The first two are shown in figure~\ref{fig:masqmail-typical-usage}.

162 \index{masqmail!common setups}

163

164 \begin{figure}

165 \begin{center}

166 \includegraphics[scale=0.75]{fig/masqmail-typical-usage.eps}

167 \end{center}

168 \caption{Typical usage scenarios for \masqmail}

169 \label{fig:masqmail-typical-usage}

170 \end{figure}

171

172 Imagine an Internet-connected home network consisting of some workstations.

173

174 \begin{description}

175 \item[Scenario 1:]

176 \label{scenario1}

177 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; only host names would differ. 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.

178 \index{isp}

179 \index{pop3}

180 \index{imap}

181

182 \item[Scenario 2:]

183 \label{scenario2}

184 In the same network but with a server, one could have \masqmail\ running on the server and using simple forwarders (see section~\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.

185 \index{relay-only mta}

186 \index{isp}

187 \index{pop3}

188 \index{imap}

189

190 \item[Scenario 3:]

191 \label{scenario3}

192 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.

193 \index{isp}

194 \index{masqmail!on notebooks}

195 \end{description}

196

197

198 In general, all kinds of usage scenarios within a trusted network are possible. Important to notice is that mail can not be sent 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.

199 \index{untrusted environment}

200

201

202

203

204 \subsubsection*{Limitations}

205 \index{masqmail!limitations}

206

207 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.

208

209 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:

210 \index{open relay}

211

212 \begin{quote}

213 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.

214 \hfill\citeweb{masqmail:homepage2}

215 \end{quote}

216

217 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.

218 \index{firewall}

219

220 The Internet is the common example for an untrusted network but other networks may be untrusted, too.

221

222

223

224

225

226

227

228

229

230

231

232

233 \subsection{Features}

234

235 This thesis regards version 0.2.21 of \masqmail. This is the last version released by \person{Oliver Kurth}.

236

237

238 \subsubsection*{The source code}

239

240 \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.

241 \index{c}

242 \index{lines of code}

243 \index{base64}

244 \index{md5}

245 \index{libident}

246

247 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.

248 \index{glib}

249 \index{masqmail!dependencies}

250

251 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.

252 \index{conditional compilation}

253 \index{maildir}

254

255 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.

256 \index{mserver}

257 \index{test program}

258

259

260

261 \subsubsection*{Features}

262 \label{sec:masqmail-features}

263

264 \masqmail\ supports two channels for incoming mail:

265

266 \begin{enumerate}

267 \item Standard input which is used when \path{masqmail} (or the \path{sendmail} link) is executed on the command line

268 \item A \NAME{TCP} socket which is used by local or remote clients that talk \SMTP

269 \end{enumerate}

270 \index{sendmail!command}

271 \index{tcp socket}

272

273 The outgoing channels for mail are:

274

275 \begin{enumerate}

276 \item Direct delivery to local mailboxes (in \name{mbox} or \name{maildir} format)

277 \item Local pipes to pass mail to a program (e.g.\ to \MDA{}s or to gateways to \NAME{FAX} or \NAME{UUCP})

278 \item \NAME{TCP} sockets to transfer mail to other \MTA{}s using the \SMTP\ protocol

279 \end{enumerate}

280 \index{tcp socket}

281 \index{local delivery}

282 \index{mbox}

283 \index{maildir}

284 \index{uucp}

285 \index{fax}

286 \index{gateway}

287 \index{mda}

288 \index{pipe}

289

290 Figure~\ref{fig:masqmail-channels} shows this as a picture. (The ``online state'' input is explained a bit later.)

291

292 \begin{figure}

293 \begin{center}

294 \includegraphics[scale=0.75]{fig/masqmail-channels.eps}

295 \end{center}

296 \caption{Incoming and outgoing channels of \masqmail}

297 \label{fig:masqmail-channels}

298 \end{figure}

299

300 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}.

301 \index{openssl}

302 \index{wrapper}

303 \index{auth!smtp-auth}

304 \index{auth!smtp-after-pop}

305

306 Mail queuing is essential for \masqmail\ and thus supported of course, alias expansion is also supported.

307 \index{alias expansion}

308

309 The \masqmail\ executable can be called by various names for sendmail-com\-pa\-ti\-bi\-li\-ty 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. Furthermore does \sendmail\ support 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.

310 \index{sendmail!compatibility}

311

312 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}.

313 \index{pop3}

314

315

316

317 \subsubsection*{Online detection and online routes}

318 \label{sec:masqmail-routes}

319 \index{online routes}

320

321 \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.

322 \index{non-permanent online connection}

323

324 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.

325 \index{isp}

326

327 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.

328 \index{spam}

329

330 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:

331 \index{online state}

332

333 \begin{enumerate}

334 \item Reading from a file

335 \item Reading the output of a command

336 \item Querying an \name{mserver} system

337 \end{enumerate}

338 \index{mserver}

339

340 Each method may return a string naming the route that is online or returning nothing to indicate offline state.

341

342

343 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.

344

345

346

347

348

349

350

351

352 \section{Why \masqmail\ is worth it}

353 \index{masqmail}

354

355 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}.

356 \index{non-permanent online connection}

357 \index{qmail}

358 \index{exim}

359

360 %fixme: hikernet

361

362 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.

363 \index{masqmail!on notebooks}

364 \index{configuration}

365

366 Probably users say it best; in this case \person{Derek Broughton}:

367 \index{masqmail!users}

368

369 \begin{quote}

370 No kidding. The whole point is that you \_have\_ to have an \MTA\ and you don't

371 want to configure Postfix/Exim/Sendmail/Qmail (almost all of which I've

372 actually done).

373

374 I now use masqmail -- it's really simple, my configuration is all in debconf,

375 it's supported by whereami, and it's really simple :-)

376

377 I'm sure you can make any \MTA\ behave nicely when offline, but it was a chore

378 with all of them.

379 \hfill\citeweb[post~\#8]{ubuntuforums:simple-mailer}

380 \end{quote}

381

382 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.

383 \index{qmail}

384

385 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}:

386

387 \begin{quote}

388 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.

389 \hfill\citeweb{stosberg:low-mem-laptop}

390 \end{quote}

391 \index{isp}

392 \index{sendmail}

393 \index{masqmail!on notebooks}

394

395

396

397 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.

398

399 It is difficult to get numbers about users of Free Software because no one needs to tell anyone when he uses some software. \name{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 \name{Debian} users report their installed software\footnote{One third is a high guess as it means there would be only about 230 thousand \name{Debian} installations in total. But according to the \name{Linux Counter} \citeweb{counter.li.org} between 490 thousand and 12 million \name{Debian} users can be estimated.}, there would be in total around 150 active \masqmail\ installations in \name{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.

400 \index{Free Software}

401 \index{debian!popcon}

402 \index{masqmail!users}

403 \index{Linux Counter}

404 \index{Unix}

405

406 %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.

407

408 One thing became clear now: \masqmail\ has users. And software that is used should be developed and maintained.

409

410

411 % alternative: http://anfi.homeunix.org/sendmail/dialup10.html

412

413

414

415

416

417

418

419

420

421 \section{Problems to solve}

422 \index{masqmail!problems}

423

424 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.

425 \index{dial-up}

426

427 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.

428

429

430

431

432

433 \section{Delimitation}

434

435 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}.

436

437 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.

438 \index{pop3}

439

440 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.

441 \index{mserver}

442

443

444