comparison thesis/tex/3-MailTransferAgents.tex @ 201:013a13ee0a5f

subsections to unnumbered subsubsections
author meillo@marmaro.de
date Wed, 31 Dec 2008 17:41:13 +0100
parents ee687abf386c
children f2b8481789f6
comparison
equal deleted inserted replaced
200:2e006e8f5250 201:013a13ee0a5f
171 \caption{Comparison of MTAs} 171 \caption{Comparison of MTAs}
172 \label{tab:mta-comparison} 172 \label{tab:mta-comparison}
173 \end{table} 173 \end{table}
174 174
175 175
176 \subsection{Architecture} 176 \subsubsection*{Architecture}
177 177
178 Architecture is most important when comparing \MTA{}s. Many other properties of a program depend on its architecture. %fixme: add ref? 178 Architecture is most important when comparing \MTA{}s. Many other properties of a program depend on its architecture. %fixme: add ref?
179 Munawar \person{Hafiz} \cite{hafiz05} discusses in detail on \mta\ architecture, comparing \sendmail, \qmail, \postfix, and \name{sendmail X}. Jonathan de \person{Boyne Pollard}'s \MTA\ review \cite{jdebp} is a source too. 179 Munawar \person{Hafiz} \cite{hafiz05} discusses in detail on \mta\ architecture, comparing \sendmail, \qmail, \postfix, and \name{sendmail X}. Jonathan de \person{Boyne Pollard}'s \MTA\ review \cite{jdebp} is a source too.
180 180
181 Two different architecture types show off: monolithic and modular \mta{}s. 181 Two different architecture types show off: monolithic and modular \mta{}s.
190 190
191 Today modular \mta\ architectures are the state-of-the-art. 191 Today modular \mta\ architectures are the state-of-the-art.
192 192
193 193
194 194
195 \subsection{With focus on the future} 195 \subsubsection*{With focus on the future}
196 196
197 Section \ref{sec:what-will-be-important} tried to figure out the importances for future \MTA{}s. The four programs are compared on these (possible) future requirements now. 197 Section \ref{sec:what-will-be-important} tried to figure out the importances for future \MTA{}s. The four programs are compared on these (possible) future requirements now.
198 198
199 The first trend was provider independence, requiring easy configuration. \postfix\ seems to do best here. It used 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 very complex, including Turing-completeness, thus it needs simplification wrappers around it to provide easier configuration. There exist the \name{m4} macros to generate \path{sendmail.cf}, but adjusting the generated result by hand seems to be nessesary 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 is hardly usable without applying several patches to add basic functionality. \name{netqmail} is the community effort to help here. \exim\ has only one single configuration file (\path{exim.conf}), but it suffers most from its flexibility, like \sendmail. Flexibility and easy configuration are contrary. 199 The first trend was provider independence, requiring easy configuration. \postfix\ seems to do best here. It used 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 very complex, including Turing-completeness, thus it needs simplification wrappers around it to provide easier configuration. There exist the \name{m4} macros to generate \path{sendmail.cf}, but adjusting the generated result by hand seems to be nessesary 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 is hardly usable without applying several patches to add basic functionality. \name{netqmail} is the community effort to help here. \exim\ has only one single configuration file (\path{exim.conf}), but it suffers most from its flexibility, like \sendmail. Flexibility and easy configuration are contrary.
200 200