1.1 --- a/thesis/bib/thesis.bib	Sat Jan 31 10:50:02 2009 +0100
     1.2 +++ b/thesis/bib/thesis.bib	Sat Jan 31 15:06:43 2009 +0100
     1.3 @@ -478,3 +478,20 @@
     1.4  Doug McIlroy The Bell System Technical Journal. Bell Laboratories. M. D. McIlroy, E. N. Pinson, and B. A. Tague. ``Unix Time-Sharing System Forward''. 1978. 57 (6, part 2). p. 1902.
     1.5  
     1.6  
     1.7 +@misc{fsf:gpl,
     1.8 +	author = "Free Software Foundation, The",
     1.9 +	title = "\emph{The GNU General Public License}",
    1.10 +	year = "2007",
    1.11 +	note = "Available on the Internet: {\small\url{http://gnu.org/licenses/gpl.html} (2009-01-31)}",
    1.12 +}
    1.13 +
    1.14 +@misc{fsf:freesw-definition,
    1.15 +	author = "Free Software Foundation, The",
    1.16 +	title = "\emph{The Free Software Definition}",
    1.17 +	year = "last updated in December 2008",
    1.18 +	note = "Available on the Internet: {\small\url{http://gnu.org/philosophy/free-sw.html} (2009-01-31)}",
    1.19 +}
    1.20 +
    1.21 +
    1.22 +
    1.23 +

     2.1 --- a/thesis/tex/0-preface.tex	Sat Jan 31 10:50:02 2009 +0100
     2.2 +++ b/thesis/tex/0-preface.tex	Sat Jan 31 15:06:43 2009 +0100
     2.3 @@ -2,7 +2,7 @@
     2.4  \chapter*{Preface}
     2.5  \addcontentsline{toc}{section}{Preface}
     2.6  
     2.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 though ``real'' mail transfer agent. \masqmail\ served me well since then and I found no reasons to change.
     2.8 +This thesis is about \masqmail, a small mail transfer agent for workstations and home networks. In October 2007 I had chosen \masqmail\ for my machines because of its small size though it was a ``real'' mail transfer agent. \masqmail\ served me well since then and I have found no reasons to change.
     2.9  
    2.10  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.
    2.11  
    2.12 @@ -10,17 +10,17 @@
    2.13  
    2.14  \quad
    2.15  
    2.16 -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.
    2.17 +The overall goal of this document is to revive \masqmail\ in usage and development. \masqmail\ was not developed further in the last five years although the world of email has changed during this time. Hence quite some work needed to be done.
    2.18  
    2.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.
    2.20 +I decided to start at the basis and analyze the environment and \masqmail\ throughout to end up in concrete plans of what should be done and how it should be done to turn \masqmail\ into a modern mail transfer agent again.
    2.21  
    2.22 -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.
    2.23 +The actual implementation of the the proposed changes will follow-up this thesis. Here solutions are identified, described, discussed, and recommended but not implemented. I have been working in the code and have fixed bugs during the time I worked on the thesis, though.
    2.24  
    2.25  \quad
    2.26  
    2.27 -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.
    2.28 +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 too.
    2.29  
    2.30 -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}.
    2.31 +However, at least basic knowledge about \unix\ and C programming is a prerequisite for chapters 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}.
    2.32  
    2.33  
    2.34  
    2.35 @@ -31,17 +31,17 @@
    2.36  
    2.37  \section*{Organization}
    2.38  
    2.39 -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.
    2.40 +The document consists of six chapters, each covering a delimited part of the overall topic and building upon the content and results of previous chapters. The first three chapters lead into the topic and create a solid base where the second part builds upon. The chapters four and five form the central part of the thesis as they focus on \masqmail.
    2.41  
    2.42 -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.
    2.43 +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 known.
    2.44  
    2.45 -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.
    2.46 +Chapter 2 \textbf{analyzes the market} of electronic communication and email. This chapter gives sound reasons for the sense of future development of \masqmail\ by showing that email will remain an important technology in the future. It tries to identify future trends too.
    2.47  
    2.48 -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.
    2.49 +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 the most important ones are presented and compared.
    2.50  
    2.51  Chapter 4 \textbf{focuses on \masqmail's present and future}. It is the core of the thesis. Requirements are identified and lead to a list of pending work tasks. Then possible strategies for future development are discussed.
    2.52  
    2.53 -Chapter 5 \textbf{describes improvement plans}, which are based on decisions in chapter four, in more detail. A proposed architecture for a redesigned \masqmail\ is presented too.
    2.54 +Chapter 5 \textbf{describes improvement plans} which are based on decisions in chapter four, in more detail. A proposed architecture for a redesigned \masqmail\ is presented, too.
    2.55  
    2.56  Chapter 6 \textbf{summarizes} the most important results and closes the thesis.
    2.57  
    2.58 @@ -65,11 +65,11 @@
    2.59  References to external resources are marked using one of three styles, distinguished by the type of resource.
    2.60  
    2.61  \begin{enumerate}
    2.62 -\item References to books, articles, and similar documents looks like this: \cite{kernighan84}. The letters represent the author(s) (here \person{Kernighan} and \person{Pike}), the number represents the year of publication (here 1984).
    2.63 +\item References to books, articles, and similar documents look like this: \cite{kernighan84}. The letters represent the author(s) (here \person{Kernighan} and \person{Pike}), while the number represents the year of publication (here 1984).
    2.64  
    2.65 -\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}.
    2.66 +\item Websites are different from documents as they are less some text written by some author but more a place where information is gathered. Website may also change from time to time, thus the date of access is given to indicate the version to which was referred. References to websites have such appearance: \citeweb{masqmail:homepage}.
    2.67  
    2.68 -\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.
    2.69 +\item \name{Request for Comments} are those documents that define the Internet. They are referenced directly by their unique number. For instance: \RFC\,821.
    2.70  \end{enumerate}
    2.71  
    2.72  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.

     3.1 --- a/thesis/tex/1-Introduction.tex	Sat Jan 31 10:50:02 2009 +0100
     3.2 +++ b/thesis/tex/1-Introduction.tex	Sat Jan 31 15:06:43 2009 +0100
     3.3 @@ -1,7 +1,7 @@
     3.4  \chapter{Introduction}
     3.5  \label{chap:introduction}
     3.6  
     3.7 -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.
     3.8 +This chapter introduces some basic email concepts that are essential for understanding the remainder 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 relevance, its weaknesses are pointed out. Solving these weaknesses is the topics that is covered throughout this thesis.
     3.9  
    3.10  
    3.11  
    3.12 @@ -11,19 +11,19 @@
    3.13  
    3.14  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.
    3.15  
    3.16 -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.
    3.17 +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 as they are essential throughout the thesis.
    3.18  
    3.19  
    3.20  \subsubsection{Mail agents}
    3.21  
    3.22 -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.
    3.23 +This thesis will frequently use the three terms: \MTA, \NAME{MUA}, and \NAME{MDA}, naming the three different kinds of 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 when passing through the system.
    3.24  
    3.25  \begin{description}
    3.26  \item[\MTA:]
    3.27 -\name{Mail Transfer Agents} are the post offices for electronic mail. The basic job of an \MTA\ is to transport mail from senders to recipients, or more pedantic: from \MTA\ to \MTA. \sendmail, \exim, \qmail, \postfix, and of course \masqmail\ are \MTA{}s. \MTA{}s are explained in more detail in chapter \ref{chap:mail-transfer-agents}.
    3.28 +\name{Mail Transfer Agents} are the post offices for electronic mail. The basic job of an \MTA\ is to transport mail from senders to recipients, or more pedantic: from \MTA\ to \MTA. \sendmail, \exim, \qmail, \postfix, and, of course, \masqmail\ are \MTA{}s. \MTA{}s are explained in more detail in chapter \ref{chap:mail-transfer-agents}.
    3.29  
    3.30  \item[\NAME{MUA}:]
    3.31 -\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}.
    3.32 +\name{Mail User Agents} are the software users deal with. A user 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}.
    3.33  
    3.34  \item[\NAME{MDA}:]
    3.35  \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.
    3.36 @@ -82,15 +82,15 @@
    3.37  \section{The \masqmail\ project}
    3.38  \label{sec:masqmail}
    3.39  
    3.40 -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.
    3.41 +The \masqmail\ project was initiated 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. During the active phase of development 53 version have been released. In average, this is a new version every 20 days.
    3.42  
    3.43 -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.
    3.44 +This thesis is based on the latest release of \masqmail---version 0.2.21, dated November 2005. It was released after a 28 month gap of inactivity. The source code of 0.2.21 is the same as of 0.2.20, with only build documents modified. The homepage of \masqmail\ \citeweb{masqmail:homepage2} does not include this latest release, but it 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}.
    3.45  
    3.46 -\masqmail\ is covered by the \name{General Public License} (short: \NAME{GPL}) which qualifies it as \freesw.
    3.47 +\masqmail\ is covered by the \name{General Public License} (short: \NAME{GPL}) \cite{fsf:gpl} which qualifies it as Free Software \cite{fsf:freesw-definition}.
    3.48  
    3.49 -\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.
    3.50 +\person{Kurth} abandoned \masqmail\ after 2005 and no one adopted the project since then. Thus, the author of this thesis decided to take over responsibility for \masqmail\ now. He received \person{Kurth}'s permission to do so in private telephone conversation with \person{Kurth} on September 4, 2008.
    3.51  
    3.52 -The program's new homepage \citeweb{masqmail:homepage} is a collection of available information about this \MTA.
    3.53 +The program's new homepage \citeweb{masqmail:homepage} includes a collection of available information about this \MTA.
    3.54  
    3.55  
    3.56  
    3.57 @@ -98,7 +98,7 @@
    3.58  \subsection{Target field}
    3.59  \label{sec:masqmail-target-field}
    3.60  
    3.61 -The intention \person{Kurth} had when creating \masqmail\ is best told in his own words:
    3.62 +\person{Kurth}'s intention when creating \masqmail\ is best told in his own words:
    3.63  \begin{quote}
    3.64  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.
    3.65  \hfill\citeweb{masqmail:homepage2}
    3.66 @@ -116,7 +116,7 @@
    3.67  
    3.68  While many other \MTA{}s are general purpose \MTA{}s, \masqmail\ aims on special situations. Nevertheless, it can be used as general purpose \MTA, too. Especially this was a design goal of \masqmail: To be a replacement for \sendmail, or similar well known \MTA{}s.
    3.69  
    3.70 -\masqmail\ is designed to run on workstations and on servers in small networks, like home networks.
    3.71 +\masqmail\ is designed to run on workstations and on servers in small networks, like they are common in \NAME{SOHO}s (\name{Small Offices/Home Offices}).
    3.72  
    3.73  
    3.74  
    3.75 @@ -230,20 +230,20 @@
    3.76  
    3.77  Mail queuing is essential for \masqmail\ and thus supported of course, alias expansion is also supported.
    3.78  
    3.79 -The \masqmail\ executable can be called under various names for sendmail-compatibility reasons. As many programs expect the \MTA\ to be located at \path{/usr/lib/sendmail} or \path{/usr/sbin/sendmail}, symbolic links are pointing from there to the \masqmail\ executable. Further more does \sendmail\ supports calling it with a different name instead of supplying command line arguments. The best known of these shortcuts is \path{mailq} which is equivalent to calling it with the argument \verb+-bq+. \masqmail\ recognizes the shortcuts \path{mailq}, \path{smtpd}, \path{mailrm}, \path{runq}, \path{rmail}, and \path{in.smtpd}. The first two are inspired by \sendmail. Not implemented is the shortcut \path{newaliases} because \masqmail\ does not generate binary representations of the alias file.\footnote{A shell script named \path{newaliases} that invokes \texttt{masqmail -bi} can provide the command to satisfy software that depends on a \path{newaliases} program.} \path{hoststat} and \path{purgestat} are missing for complete sendmail-compatibility.
    3.80 +The \masqmail\ executable can be called by various names for sendmail-compatibility reasons. As many programs expect the \MTA\ to be located at \path{/usr/lib/sendmail} or \path{/usr/sbin/sendmail}, symbolic links are pointing from there to the \masqmail\ executable. Further more does \sendmail\ supports calling it with a different name instead of supplying command line arguments. The best known of these shortcuts is \path{mailq} which is equivalent to calling it with the argument \verb+-bq+. \masqmail\ recognizes the shortcuts \path{mailq}, \path{smtpd}, \path{mailrm}, \path{runq}, \path{rmail}, and \path{in.smtpd}. The first two are inspired by \sendmail. Not implemented yet is the shortcut \path{newaliases} because \masqmail\ does not generate binary representations of the alias file.\footnote{A shell script named \path{newaliases} that invokes \texttt{masqmail -bi} can provide the command to satisfy strict requirements.} \path{hoststat} and \path{purgestat} are missing for complete sendmail-compatibility.
    3.81  %masqmail: mailq, mailrm, runq, rmail, smtpd/in.smtpd
    3.82  %sendmail: hoststat, mailq, newaliases, purgestat, smtpd
    3.83  
    3.84 -Additional to the \mta\ job, \masqmail\ also offers mail retrieval services by being a \NAME{POP3} client. It can fetch mail from different remote locations dependent on the active online connection. Such functionality is especially useful in a setup like \name{Scenario 2} on page \pageref{scenario2}.
    3.85 +Additional to the \mta\ job, \masqmail\ also offers mail retrieval services by acting as a \NAME{POP3} client. It can fetch mail from different remote locations, also dependent on the active online connection. Such functionality is especially useful in a setup like \name{Scenario 2} on page \pageref{scenario2}.
    3.86  
    3.87  
    3.88  
    3.89 -\subsubsection*{Online detection and routes}
    3.90 +\subsubsection*{Online detection and online routes}
    3.91  \label{sec:masqmail-routes}
    3.92  
    3.93  \masqmail\ focuses on handling different non-permanent online connections, thus a concept of online routes is used. One may configure any number of routes to send mail. Each route can have criteria to determine if some message is allowed to be sent over it. Mail to destinations outside the local network gets queued until a suitable online connections is available.
    3.94  
    3.95 -The idea behind this concept is sending mail to the Internet through the mail server of the same \NAME{ISP} over which one had dialed in. It was quite common that \NAME{ISP}s accepted mail for relay only if it came from as online connection they managed. This means, one was not able to relay mail through the mail server of one \NAME{ISP} while being online through the connection of another \NAME{ISP}. \masqmail\ is a solution to the wish of switching the relaying mail server easily.
    3.96 +The idea behind this concept is sending mail to the Internet through the mail server of the same \NAME{ISP} over which one had dialed in. It was quite common that \NAME{ISP}s accepted mail for relay only if it came from a online connection they managed. This means, it was not possible to relay mail through the mail server of one \NAME{ISP} while being online through the connection of another \NAME{ISP}. \masqmail\ is a solution to the wish of switching the relaying mail server easily.
    3.97  
    3.98  Related is \masqmail's ability to rewrite the sender's email address dependent on which \NAME{ISP} is used. This prevents mail from being likely classified as spam.
    3.99  
   3.100 @@ -267,7 +267,7 @@
   3.101  
   3.102  
   3.103  
   3.104 -\section{Why \masqmail\ is worthy}
   3.105 +\section{Why \masqmail\ is worth it}
   3.106  
   3.107  First of all, \masqmail\ is better suited for its target field of operation (multiple non-permanent online connections) than every other \MTA. Especially is such usage easy to set up because \masqmail\ was designed for that. Many alternative \MTA{}s were not designed for those scenarios at all as the following two example show: ``Exim is designed for use on a network where most messages can be delivered at the first attempt.'' \cite[page~30]{hazel01}. ``qmail was designed for well-connected hosts: those with high-speed, always-on network connectivity.'' \cite[page9]{sill02}.
   3.108  
   3.109 @@ -289,7 +289,7 @@
   3.110  \hfill\citeweb[post~\#8]{ubuntuforums:simple-mailer}
   3.111  \end{quote}
   3.112  
   3.113 -Not to forget is \masqmail's size. It is much smaller than full-blown \MTA{}s like \sendmail, \postfix, or \exim, and still smaller than \qmail. (See section \ref{sec:mta-comparison} for details.) This makes \masqmail\ a good choice for workstations or even embedded computers.
   3.114 +Not to forget \masqmail's size. \masqmail\ is much smaller than full-blown \MTA{}s like \sendmail, \postfix, or \exim, and still smaller than \qmail. (See section \ref{sec:mta-comparison} for details.) This makes \masqmail\ a good choice for workstations or even embedded computers.
   3.115  
   3.116  Again words of a user who chose \masqmail\ as \MTA\ on his old laptop with a 75 megahertz processor and eight megabytes of \NAME{RAM}:
   3.117  \begin{quote}
   3.118 @@ -299,7 +299,7 @@
   3.119  
   3.120  
   3.121  
   3.122 -Although the development on \masqmail\ stopped in 2003 it still has its users. Having users is already reason enough for further development and maintenance. This applies especially when the software covers a niche and when requirements for such software in general changed. Both is the case for \masqmail.
   3.123 +Although the development on \masqmail\ has been stopped in 2003, \masqmail\ still has its users. Having users is already reason enough for further development and maintenance. This applies especially when the software covers a niche and when requirements for such software in general changed. Both is the case for \masqmail.
   3.124  
   3.125  It is difficult to get numbers about users of Free Software because no one needs to tell anyone when he uses some software. \debian's \name{popcon} statistics \citeweb{popcon.debian} are a try to provided numbers. For January 2009, the statistics report 60 \masqmail\ installations of which 49 are in active use. If it is assumed that one third of all \debian\ users report their installed software\footnote{One third is a high guess as it means there would be only about 230 thousand \debian\ installations in total. But according to the \name{Linux Counter} \citeweb{counter.li.org} between 490 thousand and 12 million \debian\ users can be estimated.}, there would be in total around 150 active \masqmail\ installations in \debian. \name{Ubuntu} which also does \name{popcon} statistics \citeweb{popcon.ubuntu}, counts 82 installations with 13 active ones. If here also one third of all systems submit their data, 40 active installations can be added. Including a guessed amount of additional 30 installations on other \unix\ operating systems makes about 220 \masqmail\ installations in total. Of course one person may have \masqmail\ installed on more than one computer, but a total of 150 different users seems to be realistic.
   3.126  
   3.127 @@ -320,7 +320,7 @@
   3.128  
   3.129  \section{Problems to solve}
   3.130  
   3.131 -A program that was neglected for nearly six years in a field of operation that changed during this time surely needs improvement. Security and spam have highly increased in importance since 2003. Dial-up connections became rare, instead broadband flat rates are common now. Other \MTA{}s evolved in respect to theses changes---\masqmail\ did not.
   3.132 +A program that is neglected for more than five years in a field of operation that changed during this time surely needs improvement. Security and spam have highly increased in importance since 2003. Dial-up connections became rare, instead broadband flat rates are common now. Other \MTA{}s evolved in respect to theses changes---\masqmail\ did not.
   3.133  
   3.134  The current market situation and trends for the future need to be identified. Looks at other \MTA{}s need to be taken. Required work on \masqmail\ needs to be defined in combination with the evaluation of strategies to do this work. And a plan for further development should be created.
   3.135  

     4.1 --- a/thesis/tex/abstract.tex	Sat Jan 31 10:50:02 2009 +0100
     4.2 +++ b/thesis/tex/abstract.tex	Sat Jan 31 15:06:43 2009 +0100
     4.3 @@ -3,7 +3,7 @@
     4.4  
     4.5  \section*{\centering Abstract}
     4.6  
     4.7 -\masqmail\ is a mail transfer agent for workstations and small networks, a much smaller replacement for \sendmail. It has be orphaned by its author more than five years ago and remained unchanged since then, in a world where emailing did change. Nevertheless has \masqmail\ unique advantages that makes it still a valuable software.
     4.8 +\masqmail\ is a mail transfer agent for workstations and small networks, and a small replacement for \sendmail, \postfix, and \exim\ in those cases. It has be orphaned by its author more than five years ago and remained unchanged since then, in a world where emailing did change. Nevertheless has \masqmail\ unique advantages that makes it still a valuable software.
     4.9  
    4.10  This diploma thesis is a scientific planning effort to revive \masqmail. It provides a highly structured analysis of \masqmail\ and its environment. Modern requirements for \masqmail\ are compared against the current state of the program to receive a list of pending work tasks. Further development strategies are carefully compared and discussed. Finally concrete plans and recommendations are defined with the goal of turning \masqmail\ into a modern mail transfer agent again.
    4.11