Mercurial > docs > diploma
comparison thesis/tex/1-Candidates.tex @ 70:177cf1937554
text rework
author | meillo@marmaro.de |
---|---|
date | Thu, 23 Oct 2008 13:49:07 +0200 |
parents | 821d195e4237 |
children | 6843dfd6c4fa |
comparison
equal
deleted
inserted
replaced
69:821d195e4237 | 70:177cf1937554 |
---|---|
31 | 31 |
32 | 32 |
33 \subsection{``Real'' \MTA{}s} | 33 \subsection{``Real'' \MTA{}s} |
34 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''. | 34 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''. |
35 | 35 |
36 Common to them is their focus on transfering email, while being able to act as \name{smart host}. Their variety ranges from ones very restricted to mail transfer (\name{qmail}) to others already having interfaces for adding further mail processing modules (\name{postfix})---thus everything in between the other two groups. %FIXME: are postfix and qmail good examples? | 36 Common to them is their focus on transfering 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})---thus everything in between the other two groups. %FIXME: are postfix and qmail good examples? |
37 | 37 |
38 This group is of importance in this document. The programs selected for the comparison are ``real \MTA{}s''. | 38 This group is of importance in this document. The programs selected for the comparison are ``real \MTA{}s''. |
39 | 39 |
40 | 40 |
41 | 41 |
46 \subsection{Non-\emph{sendmail-compatible} \MTA{}s} | 46 \subsection{Non-\emph{sendmail-compatible} \MTA{}s} |
47 Due to \sendmail's significance---described in section \ref{sec:sendmail}---compatiblity 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. | 47 Due to \sendmail's significance---described in section \ref{sec:sendmail}---compatiblity 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. |
48 | 48 |
49 Hence all \MTA{}s not having a \emph{sendmail-compatible} interface or not offering it as a compatibility addon, will not be covered here. | 49 Hence all \MTA{}s not having a \emph{sendmail-compatible} interface or not offering it as a compatibility addon, will not be covered here. |
50 | 50 |
51 Examples for this group are: \name{Apache James ???} %FIXME: give an example for non-sendmail-compatible (on unix) | 51 An Examples here is \name{Apache James}. %FIXME: check if correct |
52 | 52 |
53 | 53 |
54 \subsection{Non-free software} | 54 \subsection{Non-free software} |
55 Only programs being \freesw\ are regarded, because comparing \freesw\ with proprietary or commercial software is not what typical users of programs like \masqmail\ do. 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, need to be compared against other projects of similar shape. | 55 Only programs being \freesw\ are regarded, because comparing \freesw\ with proprietary or commercial software is not what typical users of programs like \masqmail\ do. 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, need to be compared against other projects of similar shape. |
56 | 56 |
60 | 60 |
61 \section{The programs regarded} | 61 \section{The programs regarded} |
62 The programs remaining are \emph{sendmail-compatible} ``smart'' \MTA{}s that focus on mail transfer and are \freesw. One would not use a program for a job it is not suited for. Therefor only \mta{}s that are mostly similar to \masqmail\ are regarded. | 62 The programs remaining are \emph{sendmail-compatible} ``smart'' \MTA{}s that focus on mail transfer and are \freesw. One would not use a program for a job it is not suited for. Therefor only \mta{}s that are mostly similar to \masqmail\ are regarded. |
63 | 63 |
64 For the comparision, five programs are taken. These are: \sendmail, \name{qmail}, \name{postfix}, \name{exim}, and \masqmail. The four alternatives to \masqmail\ are the most important representatives of the regarded group. % FIXME: add ref that affirm that | 64 For the comparision, five programs are taken. These are: \sendmail, \name{qmail}, \name{postfix}, \name{exim}, and \masqmail. The four alternatives to \masqmail\ are the most important representatives of the regarded group. % FIXME: add ref that affirm that |
65 %TODO: what about having one program as ``outsider'' ...? | |
66 | 65 |
67 Other, but not covered, group members are: %FIXME: are these all MTAs of that group? why these and not others? | 66 \name{courier-mta} is also a member of this group, being even closer to \name{groupware} than \name{postfix}. It is excluded here, because the \NAME{IMAP} and webmail parts of the mail server suite are more in focus than its \MTA. Common mail server setups even bundle \name{courier-imap} with \name{postfix}. |
68 %TODO: what about `courier-mta'? | |
69 | 67 |
70 Here follows a small introduction to each of the five. | 68 Other members are: \name{smail}, \name{zmailer}, \name{mmdf}, and more; they all are less important and rarely used. |
69 | |
70 Following is a small introduction to each of the five programs chosen for comparision. | |
71 | 71 |
72 \subsection{\sendmail} | 72 \subsection{\sendmail} |
73 \sendmail\ is the most popular \mta. Since it was one of the first \MTA{}s and was shipped by many vendors of \unix\ systems. | 73 \sendmail\ is the most popular \mta. Since it was one of the first \MTA{}s and was shipped by many vendors of \unix\ systems. |
74 | 74 |
75 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. | 75 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. |