1.1 --- a/thesis/tex/0-preface.tex	Wed Jan 28 16:49:45 2009 +0100
     1.2 +++ b/thesis/tex/0-preface.tex	Fri Jan 30 21:20:00 2009 +0100
     1.3 @@ -2,37 +2,25 @@
     1.4  \chapter*{Preface}
     1.5  \addcontentsline{toc}{section}{Preface}
     1.6  
     1.7 -This thesis is about \masqmail, a small mail transfer agent for workstations and home networks. In October 2007 I chose \masqmail\ for my machines because it is a small but ``real'' mail transfer agent. \masqmail\ served me well since then and I found no reasons to change.
     1.8 +This thesis is about \masqmail, a small mail transfer agent for workstations and home networks. In October 2007 I chose \masqmail\ for my machines because it is a small though ``real'' mail transfer agent. \masqmail\ served me well since then and I found no reasons to change.
     1.9  
    1.10 -Unfortunately, the \masqmail\ package in \debian, which is my preferred \NAME{GNU}/Linux distribution, is unmaintained since the beginning of 2008. Unmaintained packages with critical bugs are likely to get dropped out of a distribution. Although \masqmail\ had no critical bugs, this was a situation I definitely wanted to prevent.
    1.11 +Unfortunately, the \masqmail\ package in \debian, which is my preferred \NAME{GNU}/Linux distribution, is unmaintained since the beginning of 2008. Unmaintained packages are likely to get dropped out of a distribution if critical bugs appear in them. Although \masqmail\ had no critical bugs, this was a situation I definitely wanted to prevent.
    1.12  
    1.13  Using my diploma thesis as a ``power-start'' for maintaining and developing \masqmail\ in the future was a great idea. As it came to my mind I knew this is the thing I \emph{wanted} to do. --- I did it! :-)
    1.14  
    1.15 +\quad
    1.16 +
    1.17 +The overall goal of this document is to revive \masqmail\ in usage and development. \masqmail\ was not developed in the last five years although the world of email changed during this time. Hence quite some work needed to be done.
    1.18 +
    1.19 +I chose to start down at the basis and analyze the environment and \masqmail\ throughout to end in concrete plans of what should be done and how it should be done to turn \masqmail\ into a modern mail transfer agent again.
    1.20 +
    1.21 +The actual implementation of the the proposed changes goes beyond this thesis. Here are solutions identified, described, discussed, and recommended but not implemented. I did work in the code and have fixed bugs during the time I wrote on the thesis, though.
    1.22  
    1.23  \quad
    1.24  
    1.25 -The overall goal of this document is to revive \masqmail\ in usage and development. \masqmail\ was not developed in the last five years, but the world of email changed during this time. Hence quite some work needed to be done.
    1.26 +This document is primary written with an audience of \masqmail\ developers and developers of other mail transfer agents in mind. But users of \masqmail\ and everyone who is interested in email systems in general may find this thesis an interesting literature.
    1.27  
    1.28 -I chose to start down at the basis and analyze the environment and \masqmail\ throughout to end in concrete plans of what should be done and how it should be done to turn \masqmail\ into a modern mail transfer agent again.
    1.29 -
    1.30 -The actual implementation of the the proposed changes goes beyond this thesis. Here are solutions identified, described, discussed, and recommended but not implemented. I did work in the code and have fix bugs during the time I wrote on the thesis, though.
    1.31 -
    1.32 -
    1.33 -\quad
    1.34 -
    1.35 -This document is primary written with an audience of \masqmail\ developers or developers of other mail transfer agents in mind. But users of \masqmail\ and everyone who is interested in email systems in general may find this thesis an interesting literature.
    1.36 -
    1.37 -However, at least basic knowledge about \unix\ and C programming is preconditioned in chapter three, four, and five. The required knowledge about \unix\ can be gained from \person{Kernighan} and \person{Pike}'s ``The \NAME{UNIX} Programming Environment'' \cite{kernighan84}. Programming in the C language is best learned from \person{Kernighan} and \person{Ritchie}'s ``The C Programming Language'' \cite{k&r}.
    1.38 -
    1.39 -
    1.40 -
    1.41 -
    1.42 -
    1.43 -
    1.44 -%fixme: << hikernet >>
    1.45 -
    1.46 -
    1.47 -%fixme: how to get the masqmail source code
    1.48 +However, at least basic knowledge about \unix\ and C programming is preconditioned in chapter three, four, and five. \person{Kernighan} and \person{Pike}'s ``The \NAME{UNIX} Programming Environment'' \cite{kernighan84} is a valuable source to gain information about \unix. Programming in the C language is best learned from \person{Kernighan} and \person{Ritchie}'s ``The C Programming Language'' \cite{k&r}.
    1.49  
    1.50  
    1.51  
    1.52 @@ -43,11 +31,11 @@
    1.53  
    1.54  \section*{Organization}
    1.55  
    1.56 -Six chapters structure the document. Each one covers a delimited part of the overall topic and builds upon the knowledge and results of the previous ones. The first three chapters lead into the topic and create a solid base where the second part builds upon. Chapter four and five are the central part of the thesis as they focus on \masqmail.
    1.57 +Six chapters structure this document. Each one covers a delimited part of the overall topic and builds upon the knowledge and results of the previous ones. The first three chapters lead into the topic and create a solid base where the second part builds upon. Chapter four and five are the central part of the thesis as they focus on \masqmail.
    1.58  
    1.59  Chapter 1 \textbf{introduces} \masqmail\ to the reader. It presents the properties, goals, advantages, and problems of the program. Basic concepts of the email technology are also described and later assumed to be know.
    1.60  
    1.61 -Chapter 2 \textbf{analyzes the market} of electronic communication and email. This chapter provides a secure basis by showing that email will remain an important technology in the future. It tries to identify future trends too.
    1.62 +Chapter 2 \textbf{analyzes the market} of electronic communication and email. This chapter shows that email will remain an important technology in the future which is a precondition for investing effort into it. It tries to identify future trends too.
    1.63  
    1.64  Chapter 3 \textbf{deals with mail transfer agents} (\MTA{}s) which are the most important entities of the email transport structure. \MTA{}s are defined, classified, and important ones are presented and compared.
    1.65  
    1.66 @@ -81,7 +69,7 @@
    1.67  
    1.68  \item Websites differ from documents as they are less of a text written by some author but more a place where information is gathered. They are only indicated by numbers, like for example: \citeweb{masqmail:homepage}.
    1.69  
    1.70 -\item \name{Request for Comments}---the documents that define the Internet---are referenced in a third way, by specifying the unique number of the \RFC\ directly: \RFC821.
    1.71 +\item \name{Request for Comments}---the documents that define the Internet---are referenced in a third way, by specifying the unique number of the \RFC\ directly: \RFC\,821.
    1.72  \end{enumerate}
    1.73  
    1.74  The Bibliography is located at the end of the thesis. It also includes a list of the relevant \RFC{}s and how they can be retrieved.

     2.1 --- a/thesis/tex/1-Introduction.tex	Wed Jan 28 16:49:45 2009 +0100
     2.2 +++ b/thesis/tex/1-Introduction.tex	Fri Jan 30 21:20:00 2009 +0100
     2.3 @@ -1,7 +1,7 @@
     2.4  \chapter{Introduction}
     2.5  \label{chap:introduction}
     2.6  
     2.7 -This chapter first introduces some basic email concepts that are essential to understand the rest 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 worth, its problems are pointed out. These problems which are to solve are the topics that are covered throughout this thesis.
     2.8 +This chapter first introduces some basic email concepts that are essential for understanding the rest 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 worth, its problems are pointed out. These problems which are to solve are the topics that are covered throughout this thesis.
     2.9  
    2.10  
    2.11  
    2.12 @@ -9,14 +9,14 @@
    2.13  
    2.14  \section{Email prerequisites}
    2.15  
    2.16 -Electronic mail is a service on the Internet and thus, like other Internet services, defined and standardized by \RFC{}s under management of the \name{Internet Engineering Task Force} (short: \NAME{IETF}). \RFC{}s are highly technical documents and it is not expected that the readers of this thesis are familiar with them.
    2.17 +Electronic mail is a service on the Internet and thus, like other Internet services, defined and standardized by \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.
    2.18  
    2.19  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. They are assumed to be known in the rest of the thesis.
    2.20  
    2.21  
    2.22  \subsubsection{Mail agents}
    2.23  
    2.24 -This thesis will frequently use the three terms: \MTA, \NAME{MUA}, and \NAME{MDA}. The name the three different kinds of software that are the 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 trough the system.
    2.25 +This thesis will frequently use the three terms: \MTA, \NAME{MUA}, and \NAME{MDA}. They name the three different kinds of software that are the 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 trough the system.
    2.26  
    2.27  \begin{description}
    2.28  \item[\MTA:]
    2.29 @@ -26,7 +26,7 @@
    2.30  \name{Mail User Agents} are the software the user deals with. He writes and reads email with it. The \NAME{MUA} passes outgoing mail to the nearest \MTA. Also the \NAME{MUA} displays the contents of the user's mailbox. Well known \NAME{MUA}s are \name{Mozilla Thunderbird} and \name{mutt} on \unix\ systems, and \name{Microsoft Outlook} on \name{Windows}.
    2.31  
    2.32  \item[\NAME{MDA}:]
    2.33 -\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 \NAME{MDA}, but specialized ones exist: \name{procmail} and \name{maildrop} are examples.
    2.34 +\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 \NAME{MDA}, but independent ones exist: \name{procmail} and \name{maildrop} are examples.
    2.35  \end{description}
    2.36  
    2.37  \begin{figure}
    2.38 @@ -44,23 +44,23 @@
    2.39  
    2.40  \subsubsection{Mail transfer with SMTP}
    2.41  
    2.42 -Today most of the email is transferred using the \name{Simple Mail Transfer Protocol} (short: \SMTP), which is defined in \RFC821 and the successors \RFC2821 and \RFC5321. A good entry point for further information is \citeweb{wikipedia:smtp}.
    2.43 +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}.
    2.44  
    2.45  A selection of important concepts of \SMTP\ is explained here.
    2.46  
    2.47  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 gets stored for some time on each \MTA, until it is forwarded to the next \MTA.
    2.48  
    2.49 -This leads to the concept of \name{responsibility}. A mail message is always in the responsibility of one system. First it is the \NAME{MUA}. After it was transferred to the first \MTA, it takes the responsibility for the message over. The \NAME{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 \NAME{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.
    2.50 +This leads to the concept of \name{responsibility}. A mail message is always in the responsibility of one system. First it is the \NAME{MUA}. When it is transferred to an \MTA, this \MTA\ takes over the responsibility for the message too. The \NAME{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 \NAME{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.
    2.51  
    2.52 -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.
    2.53 +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.
    2.54  
    2.55  
    2.56  
    2.57  \subsubsection{Mail messages}
    2.58  
    2.59 -Mail messages consist of text in a specific format. This format is specified in \RFC822, and the successors \RFC2822 and \RFC5322.
    2.60 +Mail messages consist of text in a specific format. This format is specified in \RFC\,822, and the successors \RFC\,2822 and \RFC\,5322.
    2.61  
    2.62 -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 address(es) of the recipient(s), the date, and possibly further information. Their order is irrelevant. Headers are named after the colon separated start of those lines, for example the ``\texttt{Date:}'' header. A user may write the header himself, but normally the \NAME{MUA} does this job.
    2.63 +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 \NAME{MUA} does this job.
    2.64  
    2.65  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 \NAME{MUA}s.
    2.66  
    2.67 @@ -68,7 +68,7 @@
    2.68  
    2.69  \codeinput{input/sample-email.txt}
    2.70  
    2.71 -Email messages are put into envelopes for transfer. This concept is 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 by using mail header data. The user has not to deal with them.
    2.72 +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.
    2.73  
    2.74  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.
    2.75  
    2.76 @@ -82,32 +82,32 @@
    2.77  \section{The \masqmail\ project}
    2.78  \label{sec:masqmail}
    2.79  
    2.80 -The \masqmail\ project was 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. In total it were 53 releases, which is in average a new version every 20 days.
    2.81 +The \masqmail\ project was started 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. In total it were 53 releases which is in average a new version every 20 days.
    2.82  
    2.83 -This thesis bases on the latest release of \masqmail---version 0.2.21 from November 2005. It was released after a 28 month gap. The source code of 0.2.21 is the same as of 0.2.20, only build documents were modified. The release tarball can be retrieved from the \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}. Probably was only put into public in the \debian\ pool because \masqmail's homepage \citeweb{masqmail:homepage2} does not include it.
    2.84 +This thesis bases on the latest release of \masqmail---version 0.2.21 from November 2005. It was released after a 28 month gap. The source code of 0.2.21 is the same as of 0.2.20, only build documents were modified. The release tarball can be retrieved from the \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}. It seems as if this version was only put into public there because \masqmail's homepage \citeweb{masqmail:homepage2} does not include it.
    2.85  
    2.86 -\masqmail\ is covered by the \name{General Public License} (short: \NAME{GPL}), which qualifies it as \freesw.
    2.87 +\masqmail\ is covered by the \name{General Public License} (short: \NAME{GPL}) which qualifies it as \freesw.
    2.88  
    2.89 -\person{Kurth} abandoned \masqmail\ after 2005, and no one adopted the project since then. Thus, the author of this thesis decided to take responsibility for \masqmail\ now. He received \person{Kurth}'s permission to do so.
    2.90 +\person{Kurth} abandoned \masqmail\ after 2005 and no one adopted the project since then. Thus, the author of this thesis decided to take responsibility for \masqmail\ now. He received \person{Kurth}'s permission to do so.
    2.91  
    2.92  The program's new homepage \citeweb{masqmail:homepage} is a collection of available information about this \MTA.
    2.93  
    2.94  
    2.95  
    2.96  
    2.97 -\subsection{Target field of \masqmail}
    2.98 +\subsection{Target field}
    2.99  \label{sec:masqmail-target-field}
   2.100  
   2.101  The intention \person{Kurth} had when creating \masqmail\ is best told in his own words:
   2.102  \begin{quote}
   2.103 -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 ISPs. It replaces sendmail or other MTAs such as qmail or exim.
   2.104 +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.
   2.105  \hfill\citeweb{masqmail:homepage2}
   2.106  \end{quote}
   2.107 -It is intended to cover a specific niche: non-permanent Internet connection and different \NAME{ISP}s.
   2.108 +It is intended to cover a specific niche: non-permanent Internet connection and different \name{Internet Service Providers} (short: \NAME{ISP}s).
   2.109  
   2.110 -Although it can basically replace other \MTA{}s, it is not \emph{generally} aimed to do so. The package description of \debian\ states this more clearly by changing the last sentence to:
   2.111 +Although it can basically replace other \MTA{}s it is not \emph{generally} aimed to do so. The package description of \masqmail\ within \debian\ states this more clearly by changing the last sentence to:
   2.112  \begin{quote}
   2.113 -In these cases, MasqMail is a slim replacement for full-blown MTAs such as sendmail, exim, qmail or postfix.
   2.114 +In these cases, MasqMail is a slim replacement for full-blown \MTA{}s such as sendmail, exim, qmail or postfix.
   2.115  \hfill\citeweb{packages.debian:masqmail}
   2.116  \end{quote}
   2.117  The program is a good replacement ``in these cases'', but not generally, since is lacks essential features for running on mail servers. It is primarily not secure enough for being accessible from untrusted locations.

     3.1 --- a/thesis/tex/2-MarketAnalysis.tex	Wed Jan 28 16:49:45 2009 +0100
     3.2 +++ b/thesis/tex/2-MarketAnalysis.tex	Fri Jan 30 21:20:00 2009 +0100
     3.3 @@ -230,7 +230,7 @@
     3.4  
     3.5  
     3.6  
     3.7 -\subsection{Important in future}
     3.8 +\subsection{Importances in future}
     3.9  \label{sec:what-will-be-important}
    3.10  
    3.11  Provider independence through running an own mail server at home asks for easy configuration of the \MTA. Providers have specialists to configure the systems, but ordinary people do not. Solutions are either having some home service system for computer configuration established with specialists coming to ones home to set up the systems; like it is already common for problems with the power and water supply systems. Or configuration needs to be easy and fool-prove, to be done by the owner himself. The latter solution depends on standardized parts that fit together seamlessly. The technology must not be a problem itself. Only settings custom to the users environment should be left open for him to set. This of course needs to be doable using a simple configuration interface like a web interface. Non-technical educated users should be able to configure the system.

     4.1 --- a/thesis/tex/4-MasqmailsFuture.tex	Wed Jan 28 16:49:45 2009 +0100
     4.2 +++ b/thesis/tex/4-MasqmailsFuture.tex	Fri Jan 30 21:20:00 2009 +0100
     4.3 @@ -141,9 +141,9 @@
     4.4  	\label{fig:stunnel}
     4.5  \end{figure}
     4.6  
     4.7 -To provide encrypted incoming channels, the \MTA\ could implement encryption and listen on a port that is dedicated to encrypted \SMTP\ (\NAME{SMTPS}). This approach would be possible, but it is deprecated in favor for \NAME{STARTTLS}. \RFC3207 ``\SMTP\ Service Extension for Secure \SMTP\ over Transport Layer Security'' shows this by not mentioning \NAME{SMTPS} on port 465. Also port 465 is not even reserved for \NAME{SMTPS} anymore \citeweb{iana:port-numbers}.
     4.8 +To provide encrypted incoming channels, the \MTA\ could implement encryption and listen on a port that is dedicated to encrypted \SMTP\ (\NAME{SMTPS}). This approach would be possible, but it is deprecated in favor for \NAME{STARTTLS}. \RFC\,3207 ``\SMTP\ Service Extension for Secure \SMTP\ over Transport Layer Security'' shows this by not mentioning \NAME{SMTPS} on port 465. Also port 465 is not even reserved for \NAME{SMTPS} anymore \citeweb{iana:port-numbers}.
     4.9  
    4.10 -\NAME{STARTTLS}---defined in \RFC2487---is what \RFC3207 recommends to use for secure \SMTP. The connection then goes over port 25 (or the submission port 587), but gets encrypted as the \NAME{STARTTLS} keyword is issued. Email depends on compatibility---only encryption methods that client and server support can be used. Hence it is best to act after the recommendations of the \RFC\ documents. This means \NAME{STARTTLS} encryption should be supported for incoming and for outgoing connections.
    4.11 +\NAME{STARTTLS}---defined in \RFC\,2487---is what \RFC\,3207 recommends to use for secure \SMTP. The connection then goes over port 25 (or the submission port 587), but gets encrypted as the \NAME{STARTTLS} keyword is issued. Email depends on compatibility---only encryption methods that client and server support can be used. Hence it is best to act after the recommendations of the \RFC\ documents. This means \NAME{STARTTLS} encryption should be supported for incoming and for outgoing connections.
    4.12  
    4.13  
    4.14  

     5.1 --- a/thesis/tex/5-Improvements.tex	Wed Jan 28 16:49:45 2009 +0100
     5.2 +++ b/thesis/tex/5-Improvements.tex	Fri Jan 30 21:20:00 2009 +0100
     5.3 @@ -282,7 +282,7 @@
     5.4  The two approaches for spam handling were already presented to the reader in section \ref{sec:functional-requirements} as \RF\,8 and \RF\,9. Here they are described in more detail:
     5.5  
     5.6  \begin{enumerate}
     5.7 -\item Refusing spam during the \SMTP\ dialog. This is the way it was meant by the designers of the \SMTP\ protocol. They thought checking the sender and recipient mail addresses would be enough, but as they are forgeable it is not. More and more complex checks need to be done. Checking needs time, but \SMTP\ dialogs time out if it takes too long. Thus only limited time during the \SMTP\ dialog can be used for checking if a message seems to be spam. The advantage is that bad messages can simply get refused---no responsibility for the message is taken and no further system load is added. See \RFC2505 (especially section 1.5) for detail.
     5.8 +\item Refusing spam during the \SMTP\ dialog. This is the way it was meant by the designers of the \SMTP\ protocol. They thought checking the sender and recipient mail addresses would be enough, but as they are forgeable it is not. More and more complex checks need to be done. Checking needs time, but \SMTP\ dialogs time out if it takes too long. Thus only limited time during the \SMTP\ dialog can be used for checking if a message seems to be spam. The advantage is that bad messages can simply get refused---no responsibility for the message is taken and no further system load is added. See \RFC\,2505 (especially section 1.5) for detail.
     5.9  
    5.10  \item Checking for spam after the mail was accepted and queued. Here more processing time can be invested, thus more detailed checks can be done. But, as responsibility for messages was taken by accepting them, it is no choice to simply delete spam mail. Checks for spam do not lead to sure results, they just indicate the possibility the message is unwanted mail. \person{Eisentraut} indicates actions to take after a message is recognized as probably spam \cite[pages 18--20]{eisentraut05}. The only acceptable one, for mail the \MTA\ is responsible for, is adding further or rewriting existing header lines. Thus all further work on the message is the same as for non-spam messages.
    5.11  \end{enumerate}