1.1 --- a/thesis/tex/2-MailTransferAgents.tex	Sun Nov 23 21:58:25 2008 +0100
     1.2 +++ b/thesis/tex/2-MailTransferAgents.tex	Wed Nov 26 09:51:53 2008 +0100
     1.3 @@ -4,10 +4,6 @@
     1.4  
     1.5  The chosen programs will be presented to the reader in a short overview and with the most important facts. The next chapter will show a comparison of these programs in several disciplines.
     1.6  
     1.7 -\section{Advantages of \MTA{}s}
     1.8 -
     1.9 -<< why are they important? >> %FIXME
    1.10 -
    1.11  
    1.12  \section{Types of \MTA{}s}
    1.13  ``Mail transfer agent'' is a term covering a variety of programs. One thing is common to them: they transfer email from one \emph{thing} to another. These \emph{things} can be hosts, meaning independent machines, or protocols like \NAME{SMTP} and \NAME{UUCP}, between which mail is transfered.\footnote{\sendmail{}'s initial purpose was moving mail between \NAME{UUCP}, \NAME{SMTP}, and \name{Berknet}.}
    1.14 @@ -44,10 +40,6 @@
    1.15  
    1.16  
    1.17  
    1.18 -\subsection*{Programs to sort out}
    1.19 -
    1.20 -\name{Mail transfer agent}s can be segmented in various ways, apart from the classification above. Groups of programs wiproperties significantly different from \masqmail\ will be sorted out now.
    1.21 -
    1.22  \subsection*{Non-\emph{sendmail-compatible} \MTA{}s}
    1.23  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.
    1.24  
    1.25 @@ -253,17 +245,3 @@
    1.26  
    1.27  
    1.28  
    1.29 -\subsubsection*{masqmail stuff}
    1.30 -
    1.31 -The \masqmail\ executable can be called under various names for \name{sendmail-compatibility} reasons. This is commonly organized by creating symbolic links with with different names to the \masqmail\ executable. These are \path{/usr/lib/sendmail} and \path{/usr/sbin/sendmail} because many programs expect a \mta\ to be located there. Further more \sendmail\ provides shortcuts by calling it with a different name instead of supplying command line arguments. The best known of it is \path{mailq}, which is equivilent to calling the \MTA\ with the argument \verb+-bq+. \masqmail\ reacts to the names \path{mailq}, \path{smtpd}, \path{mailrm}, \path{runq}, \path{rmail}, and \path{in.smtpd}. The last four are an addition to \sendmail. Not implemented is the name \path{newaliases} because it is not relevant to \masqmail. To provide the command nonetheless, one may write a shell script located at \path{/usr/bin/newaliases}, that simply invokes \verb+masqmail -bi+.
    1.32 -
    1.33 -%masqmail: mailq, mailrm, runq, rmail, smtpd/in.smtpd
    1.34 -%sendmail: hoststat, mailq, newaliases, purgestat, smtpd
    1.35 -
    1.36 -\masqmail\ is written in the \NAME{C} programming language. The program, as of version 0.2.21, consists of 34 source code and eight header files, containing about 9,000 lines of code\footnote{Measured with \name{sloccount} by David A.\ Wheeler.}. Additionally, it includes a \name{base64} implementation (about 300 lines) and \name{md5} code (about 150 lines). For systems that do not provide \name{libident}, this library is distributed as well (circa 600 lines); an available shared library however has higher precedence in linking.
    1.37 -
    1.38 -The only mandatory dependency is \name{glib}---a cross-platform software utility library, originated in the \NAME{GTK+} project. It provides safer replacements for many standard library functions. (The unsafe \verb+sprintf()+ is one example.) Also it offers handy data containers, easy-to-use implementations of data structures, and much more.
    1.39 -
    1.40 -With \masqmail\ comes the small tool \path{mservdetect}; it helps setting up a configuration that uses the \name{mserver} system to detect the online state. Two other binaries get compiled for testing purposes: \path{readtest} and \path{smtpsend}. All three programms use \masqmail\ source code; they only add a file with a \verb+main()+ function each.
    1.41 -
    1.42 -\masqmail\ does not provide an interface for modules with additional functionality. There exists no add-on or module system. But the code is separated by function to the various source files, and some functional parts can be included or excluded by defining symbols. This means adding some argument (like \verb+--enable-maildir+) to the \verb+configure+ call. Thus the concerning code gets not removed by the preprocessor.

     2.1 --- a/thesis/tex/4-MasqmailsFuture.tex	Sun Nov 23 21:58:25 2008 +0100
     2.2 +++ b/thesis/tex/4-MasqmailsFuture.tex	Wed Nov 26 09:51:53 2008 +0100
     2.3 @@ -1,4 +1,4 @@
     2.4 -\chapter{\masqmail's future}
     2.5 +\chapter{\masqmail's present and future}
     2.6  
     2.7  <<  plans to get masqmail more popular again (if that is the goal) >> %FIXME
     2.8  
     2.9 @@ -16,6 +16,20 @@
    2.10  Additional to the \mta\ job, \masqmail\ also offers mail retrieval services with being a \NAME{POP3} client. Thus it can fetch mail from remote locations, dependent on the active online route.
    2.11  
    2.12  
    2.13 +\subsubsection*{masqmail stuff}
    2.14 +
    2.15 +The \masqmail\ executable can be called under various names for \name{sendmail-compatibility} reasons. This is commonly organized by creating symbolic links with with different names to the \masqmail\ executable. These are \path{/usr/lib/sendmail} and \path{/usr/sbin/sendmail} because many programs expect a \mta\ to be located there. Further more \sendmail\ provides shortcuts by calling it with a different name instead of supplying command line arguments. The best known of it is \path{mailq}, which is equivilent to calling the \MTA\ with the argument \verb+-bq+. \masqmail\ reacts to the names \path{mailq}, \path{smtpd}, \path{mailrm}, \path{runq}, \path{rmail}, and \path{in.smtpd}. The last four are an addition to \sendmail. Not implemented is the name \path{newaliases} because it is not relevant to \masqmail. To provide the command nonetheless, one may write a shell script located at \path{/usr/bin/newaliases}, that simply invokes \verb+masqmail -bi+.
    2.16 +
    2.17 +%masqmail: mailq, mailrm, runq, rmail, smtpd/in.smtpd
    2.18 +%sendmail: hoststat, mailq, newaliases, purgestat, smtpd
    2.19 +
    2.20 +\masqmail\ is written in the \NAME{C} programming language. The program, as of version 0.2.21, consists of 34 source code and eight header files, containing about 9,000 lines of code\footnote{Measured with \name{sloccount} by David A.\ Wheeler.}. Additionally, it includes a \name{base64} implementation (about 300 lines) and \name{md5} code (about 150 lines). For systems that do not provide \name{libident}, this library is distributed as well (circa 600 lines); an available shared library however has higher precedence in linking.
    2.21 +
    2.22 +The only mandatory dependency is \name{glib}---a cross-platform software utility library, originated in the \NAME{GTK+} project. It provides safer replacements for many standard library functions. (The unsafe \verb+sprintf()+ is one example.) Also it offers handy data containers, easy-to-use implementations of data structures, and much more.
    2.23 +
    2.24 +With \masqmail\ comes the small tool \path{mservdetect}; it helps setting up a configuration that uses the \name{mserver} system to detect the online state. Two other binaries get compiled for testing purposes: \path{readtest} and \path{smtpsend}. All three programms use \masqmail\ source code; they only add a file with a \verb+main()+ function each.
    2.25 +
    2.26 +\masqmail\ does not provide an interface for modules with additional functionality. There exists no add-on or module system. But the code is separated by function to the various source files, and some functional parts can be included or excluded by defining symbols. This means adding some argument (like \verb+--enable-maildir+) to the \verb+configure+ call. Thus the concerning code gets not removed by the preprocessor.
    2.27  
    2.28  
    2.29  \section{Directions to go}

     3.1 --- a/thesis/tex/5-Improvements.tex	Sun Nov 23 21:58:25 2008 +0100
     3.2 +++ b/thesis/tex/5-Improvements.tex	Wed Nov 26 09:51:53 2008 +0100
     3.3 @@ -1,5 +1,8 @@
     3.4  \chapter{Implementation}
     3.5  
     3.6 +\section{Selection}
     3.7 +<< what to really implement within the thesis >>
     3.8 +
     3.9  
    3.10  \section{topic01}
    3.11  \section{topic02}