1 \chapter{Mail transfer agents}

2

3 After having analyzed the market for electronic mail and trends for it in the last chapter, this chapter takes a look at \mta{}s, the intelligent most important parts of the email infrastructure. \MTA{}s will be grouped by similarities, and the four most popular \freesw\ \mta{}s, will be presented to the reader in a short overview and with the most important facts. At the end of this chapter a comparison of these programs in several disciplines will be done.

4

5

6

7

8 \section{Types of MTAs}

9 ``Mail transfer agent'' is a term covering a variety of programs. One thing is common to them: they transfer email from one machine to another.

10

11 This is how Bryan Costales defines a \mta\ in \cite{costales97}:

12 \begin{quote}

13 A mail transfer agent (MTA) is a highly specialized program that delivers mail and transports it between machines, like the post office.

14 \end{quote}

15 \name{The Free Dictionary} is a bit more concrete on the term: \citeweb{website:thefreedictionary}

16 \begin{quote}

17 Message Transfer Agent - (MTA, Mail Transfer Agent): Any program responsible for delivering e-mail messages. Upon receiving a message from a Mail User Agent or another MTA, [...] it [...] delivers it to any local addressees and/or forwards it to other remote MTAs (routing) for delivery to remote recipients.

18 \end{quote}

19

20 Common to all \MTA{}s is the transfer of mail to other machines; this is the actual job. Besides this similarity, \MTA{}s can be very different. Some of them have \NAME{POP3} and/or \NAME{IMAP} servers included. Some can fetch mails through these protocols. Others have have all features you can think of. And maybe there are some that do nothing else but transporting email.

21

22 Following is a classification of \mta{}s into groups of similar programs, regarding what is viewable from the outside.

23

24

25 \subsubsection*{Relay-only MTAs}

26 \label{subsec:relay-only}

27 This is the most simple kind of \MTA. It transfers mail only to defined \name{smart hosts}\footnote{\name{smart host}s are \MTA{}s that receives email and route it to the actual destination}. \name{Relay-only} \MTA{}s do not receive mail from outside the system, and they do not deliver locally.

28

29 Most \MTA{}s can be configured to act as such a \name{forwarder}. But this is usually an additional functionality.

30

31 One would use such a program to give a system the possibility to send mail, without the need to do lots of configuration. In a local network, usually the clients are set up with a \name{relay-only} \MTA, while there is one \name{mail server} that acts as a \name{smart host}. The ``dumb'' clients send mail to this one \name{mail server} which does all the work.

32

33 Examples for that group are: \name{nullmailer}, \name{ssmtp} and \name{esmtp}.

34

35

36 \subsubsection*{Groupware}

37 Normally the term ``groupware'' does not mean one single program, but a suite of programs. They build a framework which is then populated with various modules that provide actual functionality. Modules for mail transfer, file storage, calendars, resource management, instant messaging, etc., are commonly available.

38

39 One would use one of these program suites if the main work to do is not mail transfer, but providing integrated communication facilities and team working support for a group of people. The most common scenario are companies. They have \name{groupware} running to provide adequate services for their teams to work efficiently. But one may use \name{groupware} on the home server for his family members also.

40

41 Examples are: \name{Lotus Notes}, \name{Microsoft Exchange}, \name{OpenGroupware.org} and \name{eGroupWare}.

42

43

44 \subsubsection*{``Real'' MTAs}

45 There is a third type of \mta{}s in between the minimalistic \name{relay-only} \MTA{}s and the bloated \name{groupware}. Those programs may be named ``real \MTA{}s'', or ``proper \MTA{}s'', though there is no common name. They are what is meant with the term ``\mta''---programs that transfer mail between hosts.

46

47 Common to them is their focus on transferring email, while being able to act as \name{smart host}. Their variety ranges from ones mostly restricted to mail transfer (\name{qmail}) to others already having interfaces for adding further mail processing modules (\name{postfix}). They cover everything in between the other two groups. %FIXME: are postfix and qmail good examples?

48

49 This group is of importance in this document. All programs selected for the comparison in the following section are ``real \MTA{}s''. \masqmail\ is one too.

50

51

52 \subsubsection*{Other segmenting}

53 \name{Mail transfer agents} can also be split in other ways.

54 \begin{itemize}

55 \item

56 Due to \sendmail's significance---described in section \ref{sec:sendmail}---compatibility interfaces for \sendmail\ are of importance for \unix\ \MTA{}s. Being not \emph{sendmail-compatible} does not need to matter for some fields of action, but makes the program ineligible for serving as a general purpose \MTA\ on \unix\ systems. Hence being sendmail-compatible is a major property of a \mta. %todo: how many MTAs are sendmail-compatible?

57 \MTA{}s not having a \emph{sendmail-compatible} interface or not offering it as a compatibility add-on, will not be covered here. One example for such a program is \name{Apache James}. %FIXME: check if correct

58

59 \item

60 Another separation can be done between \freesw\ programs and proprietary software. Many of the \MTA{}s for \unix\ systems are \freesw. Only these are regarded in the following sections, because comparing \freesw\ with proprietary or commercial software is not what typical users of programs like \masqmail\ do. %fixme: what are typical users?

61 Comparison with those non-free programs may be a point for large \freesw\ projects, trying to step into the business world. Small projects, mostly used by individuals at home, %fixme: is this the right target field? see chap02

62 need to be compared against other projects of similar shape. The document should be seen from \masqmail's point of view---an \MTA\ for a \unix\ system on home servers, workstations, or maybe embedded platforms---so non-free software is out of the way.

63 \end{itemize}

64

65

66

67

68 \section{Popular MTAs}

69

70 This section introduces a selection of popular \MTA{}s; they are the most likely substitutes for \masqmail. All are \emph{sendmail-compatible} ``smart'' \freesw\ \MTA{}s that focus on mail transfer, as is \masqmail.

71

72 The programs chosen are: \sendmail, \name{exim}, \name{qmail}, and \name{postfix}. They are the most important representatives of the regarded group. Although \MTA\ statistics are rare, FIXME(have different results), and good data is hard to collect, these programs tend to stay near the top.

73

74 Table \ref{tab:mta-market-share} shows the Top 10 \MTA{}s of three different statistics. The first published by \name{O'ReillyNet} in YYYY \citeweb{oreillynet:mta-stats} , the second by \name{Mailradar.com} from YYYY \citeweb{mailradar:mta-stats} , and the third by \textsc{Daniel~J.\ Bernstein} (the author of \name{qmail}) done in 2001 \citeweb{djb:mta-stats}.

75

76 \begin{table}

77 \begin{center}

78 \input{input/mta-market-share.tex}

79 \end{center}

80 \caption{Market share of \MTA{}s}

81 \label{tab:mta-market-share}

82 \end{table}

83

84 Other members of the same group are: \name{smail}, \name{zmailer}, \name{mmdf}, and \name{courier-mta}. They all are less important and rarely used, thus ommited here.

85

86

87 Now follows a small introduction to the five programs chosen for comparison, except \masqmail\ which already was introduced in chapter \ref{chap:introduction}. Longer introductions, including analysis and comparison, were written by \textsc{Jonathan de Boyne Pollard} \citeweb{jdebp}.

88

89

90

91 \subsubsection*{sendmail}

92 \label{sec:sendmail}

93 \sendmail\ is the most popular \mta, since it was one of the first and was shipped as default \MTA{}s by many vendors of \unix\ systems. %fixme: ref

94

95 The program was written by Eric Allman as the successor of his program \name{delivermail}. \sendmail\ was first released with \NAME{BSD} 4.1c in 1983. Allman was not the only one working on the program. Other people developed own versions of it and a variety of flavors came up, especially in the late eighties when Allman was inactive. %fixme: ref

96

97 \sendmail\ is focused on transferring mails between different protocols and networks, this lead to a very flexible (though complex) configuration.

98

99 The latest version is 8.14.3 from May 2008. The program is distributed under the \name{Sendmail License} as both, \freesw\ and proprietary software of \name{Sendmail, Inc.}.

100

101 Further development will go into the project \name{MeTA1} (the former name was \name{sendmail X}) which succeeds \sendmail.

102

103 More information can be found on the \sendmail\ homepage \citeweb{sendmail:homepage}.

104

105

106

107 \subsubsection*{exim}

108 \label{sec:exim}

109 \name{exim} was started in 1995 by Philip Hazel at the \name{University of Cambridge}. It is forked of \name{smail-3}, and inherited the monolithic architecture, similar to \sendmail's. But having no separation of the individual components of the system, like \name{qmail} and \name{postfix} have, did not hurt. Its security is comparably good. %fixme: ref

110

111 \name{exim} is highly configurable, especially in the field of mail policies. This makes it easy to specify how mail is routed through the system and who is allowed to send email to whom. Also interfaces for integration of virus and spam check programs are provided by design. %fixme: ref

112

113 The program is \freesw, released under the \GPL. The latest stable version is 4.69 from December 2007.

114

115 One finds \name{exim} on its homepage \citeweb{exim:homepage}.

116

117

118

119 \subsubsection*{qmail}

120 \label{sec:qmail}

121 \name{qmail} is seen by its community as ``a modern SMTP server which makes sendmail obsolete''.%fixme: ref

122 It was written by Daniel~J.\ Bernstein starting in 1995. His primary goal was to create a secure \MTA\ to replace the popular, but vulnerable, \sendmail. %fixme: ref

123

124 \name{qmail} first introduced many innovative concepts in \mta\ design and is generally seen as the first security-aware \MTA\ developed. %fixme:ref

125 %fixme: what about mmdf?

126

127 Since November 2007, \name{qmail} is released in the \name{public domain} which makes it \freesw. The latest release is 1.03 from July 1998.

128

129 The programs homepages are \citeweb{qmail:homepage1} and \citeweb{qmail:homepage2}. Further information about \name{qmail} is available with Dave Sill's ``Life with qmail'' \citeweb{lifewithqmail}.

130

131

132

133 \subsubsection*{postfix}

134 \label{sec:postfix}

135 The \name{postfix} project was started in 1999 at \name{IBM research}, then called \name{VMailer} or \name{IBM Secure Mailer}. Wietse Venema's program ``attempts to be fast, easy to administer, and secure. The outside has a definite Sendmail-ish flavor, but the inside is completely different.''\citeweb{postfix:homepage} In fact, \name{postfix} was mainly designed after qmail's architecture to gain security. But in contrast to \name{qmail} it aims much more on being fast and full-featured.

136

137 Today \name{postfix} is taken by many \unix\ systems and \gnulinux\ distributions as default \MTA.

138

139 The latest stable version is numbered 2.5.5 from August 2008. \name{postfix} is covered by the \name{IBM Public License 1.0} which is a \freesw\ license.

140

141 Additional information is available on the program's homepage \citeweb{postfix:homepage}.

142

143

144

145

146

147

148 \section{Comparison of MTAs}

149

150 This section tries not to provide an overall \MTA\ comparison, because this is already done by others. Remarkable are the one by Shearer \cite{shearer06} and an email discussion on the mailing list \name{plug@lists.q-linux.com} \citeweb{plug:mtas}. Tabulary overviews may be found at \citeweb{mailsoftware42} and \citeweb{wikipedia:comparison-of-mail-servers}.

151

152 Here provided is an overview on a selection of important properties, covering the four previously introduced programs. The data comes from the above stated sources and is collected in table \ref{tab:mta-comparison}.

153

154

155

156 \begin{table}

157 \begin{center}

158 \input{input/mta-comparison.tex}

159 \end{center}

160 \caption{Comparison of MTAs}

161 \label{tab:mta-comparison}

162 \end{table}

163

164

165

166 \subsection{About architecture}

167

168 Hafiz \cite{hafiz05} discusses in detail on \mta\ architecture (comparing \sendmail, \name{qmail}, \name{postfix}, and \name{sendmail X}).

169

170

171 \url{http://archives.neohapsis.com/archives/postfix/2006-07/1762.html} %sloc evolution of postfix, sendmail, qmail

172

173

174

175 \subsection{Security comparison}

176

177

178

179

180

181

182 \paragraph{Ref back to \ref{sec:what-will-be-important}}

183

184 provider indepencence -> easy config:

185 \sendmail\ and \name{qmail} appear to have bad positions at this point. Their configuration is complex, thus they would need simplification wrappers around them to provide easy configuration.

186

187 performance not so important:

188 \name{postfix} focuses much on performance, this might not be an important point then.

189

190 security:

191 It seems as if all widely used \mta{}s provide good security nowadays. \name{qmail}'s architecture, also used in \name{postfix}, is generally seen to be conceptually more secure, however.

192

193

194

195 \paragraph{local mail delivery}

196 But for example delivery of mail to local users is \emph{not} what \mta{}s should care about, although most \MTA\ are able to deliver mail, and many do. (\name{mail delivery agents}, like \name{procmail} and \name{maildrop}, are the right programs for this job.)

197

198

199 \paragraph{various protocols}

200 protocols like \NAME{SMTP} and \NAME{UUCP}, between which mail is transferred.\footnote{\sendmail{}'s initial purpose was moving mail between \NAME{UUCP}, \NAME{SMTP}, and \name{Berknet}.}

201

202

203

204

205

206

207

208

209 << complexity >> << security >> << simplicity of configuration and administration >> << flexibility of configuration and administration >> << code size >> << code quality >> << documentation (amount and quality) >> << community (amount and quality) >> << used it myself >> << had problems with it >>

210

211

212 << quality criteria >> << standards of any kind >> << how to compare? >> << (bewertungsmatrix) objectivity >> << how many criteria for ``good''? >>