
meillo@89: \chapter{Mail transfer agents}
meillo@254: \label{chap:mail-transfer-agents}
meillo@89: 
meillo@377: After having analyzed the market for email and having identified upcoming trends, in the last chapter; this chapter takes a look at \MTA{}s---the intelligent nodes and thus the most important parts of the email infrastructure. The \MTA{}s will be grouped by similarities first. Then the four most popular Free Software \MTA{}s will be presented to the reader in a short overview and with the most important facts. The end of this chapter is a short comparison of these programs.
meillo@89: 
meillo@117: 
meillo@89: 
meillo@89: 
meillo@120: \section{Types of MTAs}
meillo@377: ``Mail transfer agent'' is a term that covers a variety of programs. One thing is common to them: They transfer email from a sender to one or many recipients.
meillo@89: 
meillo@373: This is how \person{Bryan Costales} defines an \MTA:
meillo@377: 
meillo@117: \begin{quote}
meillo@217: A mail transfer agent (\MTA) is a highly specialized program that delivers mail and transports it between machines, like the post office.
meillo@218: \hfill\cite{costales97}
meillo@117: \end{quote}
meillo@377: 
meillo@217: \name{The Free Dictionary} is a bit more concrete on the term:
meillo@377: 
meillo@117: \begin{quote}
meillo@217: 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 \MTA{}s (routing) for delivery to remote recipients.
meillo@218: \hfill\citeweb{website:thefreedictionary}
meillo@117: \end{quote}
meillo@89: 
meillo@259: \person{Dent} and \person{Hafiz} agree \cite[page 19]{dent04} \cite[pages 3-5]{hafiz05}.
meillo@259: 
meillo@377: Common to all \MTA{}s is the transport of mail; 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 all features one can think of. And maybe there are some that do nothing else but transporting email.
meillo@89: 
meillo@373: Following is a classification of \MTA{}s into groups of similar programs, regarding what is viewable from the outside.
meillo@117: 
meillo@117: 
meillo@120: \subsubsection*{Relay-only MTAs}
meillo@89: \label{subsec:relay-only}
meillo@377: 
meillo@377: Also called \name{forwarders}. This is the most simple kind of an \MTA. It transfers mail only to defined \name{smart hosts}\footnote{\name{smart host}s are mail servers that receive email and route it to the actual destination.}. Relay-only \MTA{}s do not receive mail from outside the system and they do not deliver locally. All they do is transfer mail to a specified smart host for further relay.
meillo@89: 
meillo@89: Most \MTA{}s can be configured to act as such a \name{forwarder}. But this is usually an additional functionality.
meillo@89: 
meillo@377: One uses this kind of \MTA\ to give a system the possibility to send mail without the need to do a lot of configuration. In a local network, usually the clients are set up with relay-only \MTA{}s, while there is one mail server that acts as a smart host. The ``dumb'' clients send mail to this mail server which does all further work.
meillo@89: 
meillo@377: Example programs in that group are: \name{nullmailer}, \name{ssmtp}, and \name{esmtp}.
meillo@89: 
meillo@89: 
meillo@117: \subsubsection*{Groupware}
meillo@377: 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 the actual functionality. Modules for mail transfer, file storage, calendars, resource management, Instant Messaging, and more, are commonly available.
meillo@89: 
meillo@377: These program suites are used if the main work to do is providing integrated communication facilities and team working support for a group of people. Mail transfer is only one part of the problem to solve. The most common scenario are companies. They use \name{groupware} to provide adequate services for their teams to work efficiently. But one may use \name{groupware} on the home server for the family members too.
meillo@89: 
meillo@377: Examples for groupware are: \name{Lotus Notes}, \name{Microsoft Exchange}, and \name{OpenGroupware.org}.
meillo@89: 
meillo@89: 
meillo@120: \subsubsection*{``Real'' MTAs}
meillo@373: There is a third type of \MTA{}s in between the minimalistic \name{relay-only} \MTA{}s and the feature loaded \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 ``mail transfer agent''---programs that transfer mail between hosts.
meillo@89: 
meillo@377: Common to them is their focus on the email transfer, while they are able to act as smart hosts. Their variety ranges from ones mostly restricted to mail transfer (e.g.\ \qmail) to others having interfaces for adding further mail processing modules (e.g.\ \postfix). This group covers everything in between the other two groups.
meillo@89: 
meillo@377: \name{Real} \MTA{}s include \sendmail, \exim, \qmail, and \postfix.
meillo@89: 
meillo@89: 
meillo@117: \subsubsection*{Other segmenting}
meillo@377: \MTA{}s can also be split in other ways.
meillo@308: 
meillo@377: Due to \sendmail's significance in the early times of email, compatibility interfaces to \sendmail\ are important for Unix \MTA{}s. The reason is that many mail applications simply assume the \sendmail\ \MTA\ to be installed on the system. Being not \name{sendmail-compatible} may not 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 an \MTA. \MTA{}s without \name{sendmail-compatible} interfaces, or at least compatibility add-ons, will not be covered here. One example for such a program is \name{Apache James}.  %FIXME: check if correct
meillo@89: 
meillo@377: Another separation can be done between Free Software \MTA{}s and proprietary ones. Many of the \MTA{}s for Unix systems are Free Software. Only these are regarded throughout this thesis, because comparing Free Software with proprietary or commercial software is not what typical users of programs like \masqmail\ do. Comparison with non-free programs may be a point for large Free Software projects that try to step into the business world. Small projects, mostly used by individuals at home, need to be compared against other projects of similar shape. The document is seen from \masqmail's point of view---an \MTA\ for Unix systems on home servers and workstations---so non-free software is out of the way.
meillo@89: 
meillo@89: 
meillo@89: 
meillo@89: 
meillo@265: 
meillo@265: 
meillo@265: \subsubsection*{\masqmail's position}
meillo@265: 
meillo@377: Now, where does \masqmail\ fit in? It is not groupware nor a simple forwarder, thus it belongs to the ``real \MTA{}s''. Additionally, it is Free Software and is sendmail-compatible to a large degree. This makes it similar to \sendmail, \exim, \qmail, and \postfix. \masqmail\ is intended to be a replacement for those \MTA{}s.
meillo@265: 
meillo@378: But: It was not designed to be used as a general replacement for them. (See: section~\ref{sec:masqmail-target-field}) In fact, \masqmail\ is only a replacement \emph{in some situations}. This primary excludes working in an untrusted environment.
meillo@265: 
meillo@265: 
meillo@265: 
meillo@265: 
meillo@265: 
meillo@265: 
meillo@265: 
meillo@265: 
meillo@265: 
meillo@265: 
meillo@120: \section{Popular MTAs}
meillo@89: 
meillo@308: This section introduces a selection of popular \MTA{}s; they are the most likely substitutes for \masqmail. All are sendmail-compatible ``smart'' \freesw\ \MTA{}s that focus on mail transfer, as is \masqmail.
meillo@89: 
meillo@377: The programs chosen to be compared are: \sendmail, \exim, \qmail, and \postfix. They are the most important representatives of the regarded group.
meillo@117: 
meillo@145: 
meillo@145: \subsection{Market share analysis}
meillo@323: \label{sec:market-share}
meillo@145: 
meillo@377: \MTA\ statistics are rare, differ, and good data is hard to collect. These points are bad if good statistics are wanted. Thus it is obvious there are only few available.
meillo@217: 
meillo@378: Table~\ref{tab:mta-market-share} shows the most used \MTA{}s determined by three different statistics. The first was done by \person{Daniel~J.\ Bernstein} (the author of \qmail) in 2001 \cite{bernstein01}. The second is by \person{Simpson} and \person{Bekman} in 2007 and was published on \name{O'ReillyNet} \cite{simpson07}. And the third is from \name{MailRadar.com} with unknown date\footnote{The footer of the website shows ``Copyright 2007'' but more likely does this refer to the whole website.} \citeweb{mailradar:mta-stats}.
meillo@117: 
meillo@130: \begin{table}
meillo@130: 	\begin{center}
meillo@271: 		\input{tbl/mta-market-share.tbl}
meillo@130: 	\end{center}
meillo@130: 	\caption{Market share of \MTA{}s}
meillo@130: 	\label{tab:mta-market-share}
meillo@130: \end{table}
meillo@89: 
meillo@373: All surveys show high market shares for the four \MTA{}s: \sendmail, \exim, \qmail, and \postfix. Only the \name{Microsoft} mail server software and \name{IMail} have comparable large shares. Other Free Software \MTA{}s (\name{smail}, \name{zmailer}, \NAME{MMDF}, \name{courier-mta}) are less important and seldom used.
meillo@130: 
meillo@377: The three surveys base on different data. \person{Bernstein} took 1\,000\,000 randomly chosen \NAME{IP} addresses, containing 39\,206 valid hosts; 958 of them accepted \NAME{SMTP} connections. The \name{O'ReillyNet} survey used only domains owned by companies; in total 400\,000 hosts. \name{MailRadar} scanned 2\,818\,895 servers, leading to 59\,209 accepted connections.
meillo@130: 
meillo@377: All surveys show \sendmail\ to be the most popular \MTA. \postfix, \qmail, and \exim\ are among the top six in each. \exim\ has slightly smaller shares than the other two. The four programs together share more than half of the market according to \person{Bernstein} and the \name{MailRadar} statistics. \name{O'ReillyNet} has their share to be somewhere between a third and the half. This uncertainty comes from the large amount of unidentifiable \MTA{}s.
meillo@143: 
meillo@377: The 22 percent of \name{mail security layers} in the \name{O'ReillyNet} survey is remarkable. Mail security layers are software guards between the network and the \MTA\ that filter unwanted mail before it reaches the \MTA. This increases security by filtering malicious content and by blocking attacks against the \MTA. The large share here may be a result of only regarding business mail servers. The problem concerning the survey is the disguise of the \MTA{}s that run behind the security layer. It seems wrong to assume equal shares for the \MTA{}s behind the guards as for the unguarded \MTA{}s, because mail security layers will be more often used to guard weak \MTA{}s, as strong ones do not need them so much. This needs to be kept in mind when looking at the \name{O'ReillyNet} survey.
meillo@145: 
meillo@377: The date of the \name{Mailradar} statistics is not known; a mail to \name{Mailradar} with a request for information has not been replied, unfortunately. However, it seems quite sure that the statistics were published after 2001, caused by the \sendmail\ and \postfix\ shares. But to decide whether before or after the one from \name{O'ReillyNet} would be just guessing. Possibly it receives constant input and thus displays a current state.
meillo@145: 
meillo@145: 
meillo@145: \subsection{The four major Free Software MTAs}
meillo@143: 
meillo@378: Now follows a small introduction to the four programs chosen for comparison. \masqmail\ is not presented here as it was already introduced in chapter~\ref{chap:introduction}. Longer introductions, including analysis and comparison, were written by \person{Jonathan de Boyne Pollard} \cite{jdebp}.
meillo@89: 
meillo@117: 
meillo@117: 
meillo@120: \subsubsection*{sendmail}
meillo@89: \label{sec:sendmail}
meillo@89: 
meillo@377: \sendmail\ is the best known \MTA, since it was one of the first and surely the one that made \MTA{}s popular. It also was shipped as default \MTA{}s by many Unix system vendors \citeweb{wikipedia:sendmail}.
meillo@89: 
meillo@377: The program was written by \person{Eric Allman} as the successor of his program \name{delivermail}. \person{Allman} was not the only one who was 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 \cite[page~5]{vixie01}.
meillo@89: 
meillo@377: \sendmail\ is designed to transfer mails between different protocols and networks, this lead to a very flexible, though complex, configuration.
meillo@377: 
meillo@377: The program was first released with \NAME{BSD} 4.1c in 1983. The latest version is 8.14.3 from May 2008. The program is distributed under the \name{Sendmail License} as both, free and proprietary software.
meillo@318: %fixme: write about its importance and about sendmail-compat
meillo@312: 
meillo@378: Further development will go into the project \name{MeTA1} which succeeds \sendmail. The former name of this new project was \name{sendmail~X}.
meillo@89: 
meillo@377: More information can be found on the \sendmail\ homepage \citeweb{sendmail:homepage} and in the, so called, \name{Bat Book} \cite{costales97}.
meillo@89: 
meillo@89: 
meillo@117: 
meillo@120: \subsubsection*{exim}
meillo@117: \label{sec:exim}
meillo@117: 
meillo@377: \exim\ was started in 1995 by \person{Philip Hazel} at the \name{University of Cambridge}. It is a fork of \name{smail-3}, and inherited the monolithic architecture which is similar to \sendmail's. But having no architecture-given separation of the individual components of the system did not hurt. Its security is quite good \cite{blanco05}.
meillo@377: 
meillo@377: \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. Interfaces to integrate spam and malware checkers are provided by design too.
meillo@117: 
meillo@321: The program is \freesw, released under the \NAME{GPL}. The latest stable version is 4.69 from December 2007.
meillo@117: 
meillo@217: One finds \exim\ on its homepage \citeweb{exim:homepage}. The standard literature is \person{Hazel}'s \exim\ book \cite{hazel01}.
meillo@117: 
meillo@117: 
meillo@117: 
meillo@120: \subsubsection*{qmail}
meillo@89: \label{sec:qmail}
meillo@377: 
meillo@377: \qmail\ is seen by its community as ``a modern \SMTP\ server which makes sendmail obsolete'' \citeweb{qmail:homepage2}. It was written by \person{Daniel~J.\ Bernstein}, starting in 1995. His primary goal was to create a secure \MTA\ to replace the popular, but vulnerable, \sendmail. His own words are: ``This is why I started writing qmail: I was sick of the security holes in sendmail and other \MTA{}s.'' \citeweb{qmail:homepage1}.
meillo@89: 
meillo@373: \qmail\ first introduced many innovative concepts in \MTA\ design. The most obvious contrast to \sendmail\ and \exim\ is its modular design. But \qmail\ was not the first modular \MTA. \NAME{MMDF}, which predates even \sendmail, was modular too. Regardless of \NAME{MMDF}'s modular architecture, \qmail\ is generally seen as the first security-aware \MTA\ \citeweb{wikipedia:qmail}.
meillo@89: 
meillo@377: The latest release of \qmail\ is version 1.03 from July 1998. Afterwards, in November 2007, \qmail's source was put into the \name{public domain}. This made it Free Software.
meillo@89: 
meillo@377: Because of \person{Bernstein}'s inactivity, though the requirements changed since 1998, ``[a] motley krewe of qmail contributors (see the \NAME{README}) has put together a netqmail-1.06 distribution of qmail. It is derived from Daniel Bernstein's qmail-1.03 plus bug fixes, a few feature enhancements, and some documentation.'' \citeweb{netqmail:homepage}.
meillo@223: 
meillo@248: \qmail's homepages are \citeweb{qmail:homepage1} and \citeweb{qmail:homepage2}. The best book about \qmail, from \person{Bernstein}'s view, is \person{Dave Sill}'s handbook \cite{sill02}. His free available guide ``Life with qmail'' is another valuable source \cite{lifewithqmail}.
meillo@89: 
meillo@89: 
meillo@117: 
meillo@120: \subsubsection*{postfix}
meillo@89: \label{sec:postfix}
meillo@377: The \postfix\ project started in 1999 at \NAME{IBM} \name{research}, then called \name{VMailer} or \NAME{IBM} \name{Secure Mailer}. \person{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, \postfix\ was mainly designed after qmail's architecture to gain security. But in contrast to \qmail\ it aims much more on being fast and full-featured.
meillo@89: 
meillo@132: Today \postfix\ is taken by many \unix\ systems and \gnulinux\ distributions as default \MTA.
meillo@89: 
meillo@377: The latest stable version is numbered 2.5.6 from December 2008. \postfix\ is covered by the \NAME{IBM} \name{Public License 1.0} which is a Free Software license.
meillo@89: 
meillo@217: Additional information can be retrieved from the program's homepage \citeweb{postfix:homepage}. \person{Dent}'s \postfix\ book \cite{dent04} claims to be ``the definitive guide'', and it is.
meillo@89: 
meillo@89: 
meillo@89: 
meillo@89: 
meillo@89: 
meillo@89: 
meillo@120: \section{Comparison of MTAs}
meillo@308: \label{sec:mta-comparison}
meillo@89: 
meillo@312: This section does not try to provide a throughout \MTA\ comparison, because this is already done by others. Remarkable comparisons are the one by \person{Dan Shearer} \cite{shearer06} and a discussion on the mailing list \name{plug@lists.q-linux.com} \cite{plug:mtas}. Tabular overviews may be found at \citeweb{mailsoftware42}, \citeweb{wikipedia:comparison-of-mail-servers}, and \cite[section 1.9]{lifewithqmail}.
meillo@89: 
meillo@378: Here provided is an overview on important properties of the four previously introduced \MTA{}s. The data comes from the above stated sources and is collected in table~\ref{tab:mta-comparison}\footnote{The lines of code were measured with \person{David~A.\ Wheeler}'s \name{sloccount} \citeweb{sloccount}.}.
meillo@126: 
meillo@117: \begin{table}
meillo@126: 	\begin{center}
meillo@271: 		\input{tbl/mta-comparison.tbl}
meillo@126: 	\end{center}
meillo@312: 	\caption{Comparison of \MTA{}s}
meillo@126: 	\label{tab:mta-comparison}
meillo@117: \end{table}
meillo@89: 
meillo@89: 
meillo@201: \subsubsection*{Architecture}
meillo@89: 
meillo@378: Architecture is most important when comparing \MTA{}s. Many other properties of a program depend on its architecture. \person{Munawar Hafiz} discusses in detail on \MTA\ architecture, comparing \sendmail, \qmail, \postfix, and \name{sendmail~X} \cite{hafiz05}. \person{Jonathan de Boyne Pollard}'s \MTA\ review \cite{jdebp} is a source too.
meillo@89: 
meillo@373: Two different architecture types show off: monolithic and modular \MTA{}s.
meillo@130: 
meillo@377: Monolithic \MTA{}s are \sendmail, \name{smail}, \exim, and \masqmail. They all consist of one single \emph{setuid root}\footnote{\emph{setuid} lets a program run with the rights of its owner, here root. This is considered to be a security risk. Thus it it should be avoided if possible.} binary which does all the work.
meillo@130: 
meillo@377: Modular \MTA{}s are \NAME{MMDF}, \qmail, \postfix, and \name{MeTA1}. They consist of several programs, each doing only a part of the overall job. The different programs run with the least permissions they need, \emph{setuid root} can be avoided completely.
meillo@130: 
meillo@378: The architecture does not directly define the program's security, but ``[t]he goal of making a software secure can be better achieved by making the design simple and easier to understand and verify'' \cite[chapter~6]{hafiz05}. \exim, though being monolithic, has a fairly clean security record. But it is very hard to keep the security up as the program growth. \person{Wietse Venema} (the author of \postfix) says, it was the architecture that enabled \postfix\ to grow without running into security problems \cite[page 13]{venema:postfix-growth}.
meillo@130: 
meillo@217: The modular design, with each sub-program doing one part of the overall job, conforms to the \name{Unix Philosophy}. The Unix Philosophy \cite{gancarz95} demands ``small is beautiful'' and ``make each program do one thing well''. Monolithic \MTA{}s fail here.
meillo@130: 
meillo@373: Today modular \MTA\ architectures are the state-of-the-art.
meillo@89: 
meillo@89: 
meillo@217: \subsubsection*{Spam checking and content processing}
meillo@89: 
meillo@377: Spam and malware increased during the last years. Today it is important for an \MTA\ to be able to provide checking for bad mail. This can be done by implementing functionality into the \MTA\ or by invoking external programs to do this job.
meillo@89: 
meillo@377: \sendmail\ invented \name{milter}\footnote{``milter'' is a common abbreviation for ``sendmail mail filter \NAME{API}''.}, which is used to interface external programs of various kind. \postfix\ adopted the \name{milter} interface but is also able to easily include scanning modules into its modular structure. \qmail\ is pretty old and did not evolve with the changing market situation. Anyhow, its modular structure enables external scanners to be included into \qmail. \exim\ has the advantage that it was designed with the goal to provide extensive scanning facilities; it is therefore very good suited to scan itself or invoke external scanners.
meillo@89: 
meillo@313: 
meillo@377: \subsubsection*{Future trends}
meillo@89: 
meillo@378: In chapter~\ref{chap:market-analysis}, it was tried to figure out trends and future requirements for \MTA{}s. The four programs are compared on these possible future requirements now.
meillo@126: 
meillo@377: \paragraph{Provider independence}
meillo@377: The first trend was provider independence, which requires easy configuration. \postfix\ seems to do best here. It uses primary two configuration files (\path{master.cf} and \path{main.cf}) which are easy to manage. \sendmail\ appears to have a bad position. Its configuration file \path{sendmail.cf} is cryptic and very complex (it has legendary Turing-completeness) thus it needs simplification wrappers around it to provide easier configuration. They exist in form of the \name{m4} macros that generate the \path{sendmail.cf} file. Unfortunately, adjusting the generated result by hand appears to be necessary for non-trivial configurations. \qmail's configuration files are simple but the whole system is complex to set up; it requires various system users and \qmail\ is hardly usable without applying several patches that add functionality which is required nowadays. \name{netqmail} is the community's effort to help in the latter point. \exim\ has only one single configuration file (\path{exim.conf}) which suffers most from its flexibility---like in \sendmail's case. Flexibility and easy configuration are almost always contrary goals.
meillo@217: 
meillo@377: \paragraph{Performance}
meillo@377: As second trend, the decreasing necessity for high performance was identified. This goes along with the move of \MTA{}s from service providers to home servers. \postfix\ focuses much on performance, this might not be an important point in the future. Of course there will still be the need for high performance \MTA{}s, but a growing share of the market will not require high performance. Energy and space efficiency is related to performance; it is a similar goal in a different direction. But optimization, be it for performance or other efficiencies, is often in contrast to simplicity and clarity; these two improve security. Optimizing does in most times decrease the simplicity and clarity. Simple \MTA{}s that do not aim for high performance are what is needed in future. The simple design of \qmail\footnote{\qmail\ is still fast} is a good example.
meillo@313: 
meillo@377: \paragraph{Security}
meillo@377: The third trend (even more security awareness) is addressed by each of the four programs. It seems as if all widely used \MTA{}s provide good security nowadays. Even \sendmail\ can be configured to be secure today. However, the modular architecture, used by \qmail\ and \postfix, is generally seen to be conceptually more secure. \sendmail's creators have started \name{MeTA1}, a modular \MTA\ that merges the best of \qmail\ and \postfix, to replace the old \sendmail. It will be interesting to watch \exim's future---will it become modular too?
meillo@126: 
meillo@126: 
meillo@93: 
meillo@265: 
meillo@265: 
meillo@265: 
meillo@287: \section{Summary}
meillo@193: 
meillo@313: This chapter first took an overview over the field of \MTA{}s. Three major types of \MTA{}s were identified: Relay-only \MTA{}s (also called forwarders), groupware, and the ``real \MTA{}s''. \masqmail\ belongs to the last group, it is additionally sendmail-compatible and Free Software.
meillo@276: 
meillo@377: Next a look at the market shares of \MTA{}s was taken; It showed that four \MTA{}s of \masqmail's group have high importance: \sendmail, \postfix, \qmail, and \exim. Their combined share is between one third and the half of the market. The other part splits into proprietary \MTA{}s, unknown software behind mail security layers, and a reminder of really small market shares.
meillo@89: 
meillo@377: Each one of the four major Free Software \MTA{}s was presented afterwards and finally these programs were compared on some selected properties.
meillo@89: 
meillo@377: Now, the reader should have a general knowledge about those four important \MTA{}s. Further chapters will refer frequently to them.
meillo@117: 
meillo@117: 




