1.1 --- a/thesis/tex/1-Introduction.tex	Tue Jan 13 17:18:25 2009 +0100
     1.2 +++ b/thesis/tex/1-Introduction.tex	Tue Jan 13 17:18:40 2009 +0100
     1.3 @@ -81,93 +81,88 @@
     1.4  \section{The \masqmail\ project}
     1.5  \label{sec:masqmail}
     1.6  
     1.7 -<< about masqmail (some history) >>
     1.8 +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. Thoughout the next four years, he worked steadily on it, releasing new versions very few weeks. In total it were 53 releases, which means a new version in less than every 20 days in average.
     1.9  
    1.10 -(include history of email, definition of MTA and sendmail-compatibility in text)
    1.11 +This thesis bases on the latest release of \masqmail\ that was found---version 0.2.21 from November 2005. It was a release without source code changes to 0.2.20; only build documents were changed. One may retrieve it from the \debian\ package pool\footnote{The distribution tarball of \masqmail\ version 0.2.21 is located at: \url{http://ftp.de.debian.org/debian/pool/main/m/masqmail/masqmail\_0.2.21.orig.tar.gz}\,.} \citeweb{debian:packages}. It probably was never put into public anywhere else, including its homepage \citeweb{masqmail:homepage2}.
    1.12  
    1.13 -The \masqmail\ program was written by \person{Oliver Kurth}, starting in 1999. His aim was to create a small \mta\ which is especially focused on computers with dial-up connections to the internet. \masqmail\ is easy configurable for situations which are rarely solveable with the common \MTA{}s.
    1.14 +\masqmail\ is covered by the \name{General Public License} (short: \GPL), which qualifies it as \freesw.
    1.15  
    1.16 -\masqmail\ queues mail for destinations outside the local network if no connection to the internet is online. If the machine goes online, this mail is sent. Mail to local machines is sent immediately.
    1.17 +\person{Kurth} abandonned \masqmail\ after 2005, and no one addopted 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.
    1.18  
    1.19 -While the other \MTA{}s are more general purpose \MTA{}s, \masqmail\ aims on special situations only. Nevertheless can it handle ordinary mail transfers too.
    1.20 +The program's new homepage is a collection of available information about this \MTA\ \citeweb{masqmail:homepage}.
    1.21  
    1.22 -\masqmail\ is released under the \GPL, which makes it \freesw. The latest stable version is 0.2.21 from November 2005.
    1.23  
    1.24 -The program's new homepage \citeweb{masqmail:homepage} provides further information about this \MTA.
    1.25  
    1.26 -<< specify the really important external documents here >> %FIXME
    1.27  
    1.28 +\subsection{Target field of \masqmail}
    1.29  
    1.30 -
    1.31 -\subsection{Target field / When to use \masqmail}
    1.32 -
    1.33 -Its original author, \person{Oliver Kurth}, sees \masqmail\ so:
    1.34 +The intention \person{Kurth} had when creating \masqmail\ is best told in his own words:
    1.35  \begin{quote}
    1.36  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.
    1.37 +\hfill\citeweb{masqmail:homepage2}
    1.38 +\end{quote}
    1.39 +It is inteded to cover a specific niche: non-permanent internet connection and different \NAME{ISP}s.
    1.40 +
    1.41 +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:
    1.42 +\begin{quote}
    1.43 +In these cases, MasqMail is a slim replacement for full-blown MTAs such as sendmail, exim, qmail or postfix.
    1.44 +\hfill\citeweb{packages.debian:masqmail}
    1.45 +\end{quote}
    1.46 +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 accessable from untrusted locations.
    1.47 +
    1.48 +\masqmail\ is best used in home networks, which are non-permanently connected to the Internet. It is easy configurable for situations which are rarely solveable with the common \MTA{}s. Such include different handling of mail to local or remote destination and respecting different routes of being online connection. These features are explained in more detail in the following \name{Features} section on page \ref{sec:masqmail-features}. %fixme: is it still called ``features''?
    1.49 +
    1.50 +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.
    1.51 +
    1.52 +\masqmail\ is designed to run on workstations and on servers in small networks, like home networks.
    1.53 +
    1.54 +
    1.55 +
    1.56 +\subsubsection*{A typical usage scenario}
    1.57 +
    1.58 +This section describes two common setups that makes senseful use of \masqmail.
    1.59 +
    1.60 +Imagine a home network consisting of some workstations without a server. The network is connected to the internet by dial-up or broadband. Going online is initiated by computers inside the local network. \NAME{IP} addresses change at least once every day.
    1.61 +
    1.62 +Every workstation would be equiped with \masqmail. Mail transfer within the same machine or within the local net works straight forward using direkt transfer. Outgoing mail to the internet is sent, to an \name{Internet Service Provider} (short: \NAME{ISP}) for relaying whenever the router goes online. To receive mail from the Internet requires a mailbox on the \NAME{ISP}'s mail server. Mail needs to be fetched from the \NAME{ISP}'s server onto the workstation. The configuration of \masqmail\ would be the same on every computer, except different hostnames.
    1.63 +
    1.64 +In the same network but with a server, one could have \masqmail\ running on the server and using simple forwarders (see \ref{subsec:relay-only}) on the workstations to tranfer mail to the server. The server would then deliver locally or relay to an \NAME{ISP}'s server for further relay, dependent on the destination of the message. This setup does only support mail transfer to the server, but not back to a workstation. This transfer from the server to the workstations can be solvable by mounting the users mailbox from the server to the workstation, or by making the workstations fetch mail from the server.
    1.65 +
    1.66 +%fixme: what about notebooks?
    1.67 +<< notebooks >>
    1.68 +
    1.69 +Figure \ref{fig:masqmail-typical-usage} despicts the two scenarios.
    1.70 +
    1.71 +\begin{figure}
    1.72 +	\begin{center}
    1.73 +		\includegraphics[scale=0.75]{img/masqmail-typical-usage.eps}
    1.74 +	\end{center}
    1.75 +	\caption{Typical usage scenarios for \masqmail}
    1.76 +	\label{fig:masqmail-typical-usage}
    1.77 +\end{figure}
    1.78 +
    1.79 +In general, all kinds of usage scenarios within a trusted network are possible.
    1.80 +
    1.81 +
    1.82 +
    1.83 +
    1.84 +\subsubsection*{Limitations}
    1.85 +
    1.86 +Although \masqmail\ is seen as a replacement for other general purpose \MTA{}s, it should not be used on large mail servers. The reasons are that it implements only a basic subset of features, also its performance and security are not as good as provided by alternative \MTA{}s.
    1.87 +
    1.88 +The author, \person{Kurth}, warns on the old project's website about using it to accept connections from the Internet, because of the risk of being an open relay:
    1.89 +
    1.90 +\begin{quote}
    1.91 +MasqMail is not designed to run on a host with a permanent internet connection. It does not have the ability to check for spam mail and it will relay everything from everywhere to everywhere. Use another mail server such as exim for permanent connections.
    1.92 +\hfill\citeweb{masqmail:homepage2}
    1.93  \end{quote}
    1.94  
    1.95 -\masqmail\ is inteded to cover a specific niche: non-permanent internet connection and different \NAME{ISP}s.
    1.96 -
    1.97 -Although it can basically replace other \MTA{}s, it is not generally aimed to do so. The package description of \debian\citeweb{packages.debian:masqmail} states this more clearly by changing the last sentence to:
    1.98 -\begin{quote}
    1.99 -In these cases, MasqMail is a slim replacement for full-blown MTAs such as sendmail, exim, qmail or postfix.
   1.100 -\end{quote}
   1.101 -\masqmail\ is a good replacement ``in these cases'', but not generally, since is lacks features essential for running on mail servers. It is primarily not secure enough for being accessable from untrusted locations.
   1.102 -
   1.103 -The program is best used in home networks, which are non-permanently connected to the internet. \masqmail\ sends mail to local destinations, like users on the same machine and on other machines in the local net, immediately. Email to recipients outside the local net are queued when offline and sent when a online connection gets established.
   1.104 -
   1.105 -Further more does \masqmail\ respect online connections through different \NAME{ISP}s; a common thing for dial-up connections. In particular can different sender addresses be set, dependent on the \NAME{ISP} that is used. This prevents mail to be likely classified as spam.
   1.106 -
   1.107 -
   1.108 -
   1.109 -
   1.110 -\subsubsection*{\masqmail's main goal}
   1.111 -
   1.112 -\masqmail\ does have similar requirements, by being a \sendmail\ replacement, which is a basic goal of the project. The main difference is that \masqmail\ is intended to be used on workstations and in small networks, but \sendmail, \qmail, and \postfix\ are designed to run on large mail servers to handle masses of email. The author of \masqmail, \person{Kurth}, in contrast, warns on the old project's website \citeweb{masqmail:homepage2} about using it to accept connections from the Internet, because of the risk to be an open relay:
   1.113 -\begin{quote}
   1.114 -MasqMail is not designed to run on a host with a permanent internet connection. It does not have the ability to check for spam mail and it will relay everything from everywhere to everywhere. Use another mail server such as exim for permanent connections.
   1.115 -\end{quote}
   1.116  Even if some relay control will be added, ``is not designed to'' is a clear indicator for being careful. Issues like high memory consumption, low performance, and denial-of-service attacks---things not regarded by design---may cause serious problems.
   1.117  
   1.118 -Here shows a misfit off: On the one hand does \masqmail\ want to be a \sendmail\ replacement. But on the other hand, is it not designed to be used like \sendmail. If \masqmail\ is inteded to replace other \MTA{}s, then one may replace another one with it. Hence it must be secure enough. It either needs the security features or must drop the unsecure funtionality. The second option, however, leads to being \emph{no} replacement for other \MTA{}s. It is a valid decision to not be a replacement for \sendmail\ or thelike, but this is a design decision---the change of a primary goal.
   1.119 +Hence, \masqmail\ should not be used for permanent internet connections. Or at least it needs to be secured with care.
   1.120  
   1.121 -If \masqmail\ should be an \MTA\ to replace others, a switch to a better suited architecture that provides good security and extendability by design, seems required. But if \masqmail\ is wanted to cover some special jobs, not to replace common \MTA{}s, then its architecture depends on the special requirements of the specific job; \MTA\ architectures, like discussed by \person{Hafiz}, may be inadequate.
   1.122  
   1.123  
   1.124 -\subsubsection*{Full featured or stripped down}
   1.125 -
   1.126 -What future is to choose for \masqmail---one to be a full featured \MTA, or one to be a stipped down \MTA\ for special jobs?
   1.127 -
   1.128 -The critical point to discuss upon is surely the listening on a port to accepte messages from outside via \NAME{SMTP} (herafter also refered to as the \NAME{SMTP}-in channel). This feature is required for an \MTA\ to be a \name{smart host}, to relay mail. But running as deamon and listening on a port requires much more security effort, because the program is put in direct contact with attackers and other bad guys.
   1.129 -
   1.130 -\MTA{}s without \SMTP-in channels can not receive mail from arbitrary outside hosts. They are only invoked by local users. This lowers the security need a lot---however, security is a general goal and still required, but on a lower level. Unfortunately, as they do not receive mail anymore (except by local submission), they are just better \name{forwarders} that are able to send mail directly to the destination.
   1.131 -
   1.132 -This is not what \masqmail\ was intended to be. Programs that cover this purpose are available; one is \name{msmtp}.
   1.133 -
   1.134 -\masqmail\ shall be a complete \mta. It shall be able to replace ones like \sendmail.
   1.135 -
   1.136 -
   1.137 -
   1.138 -\subsubsection*{Typical usage}
   1.139 -This section describes situations that make senseful use of \masqmail.
   1.140 -
   1.141 -A home network consisting of some workstations without a server. The network is connected to the internet by dial-up or broadband. Going online is initiated by computers inside the local net. \NAME{IP} addresses change at least once every day.
   1.142 -
   1.143 -Every workstation would be equiped with \masqmail. Mail transfer within the same machine or within the local net works straight forward. Outgoing mail to the internet is sent, to the concerning \NAME{ISP} for relaying, whenever the router goes online. Receiving of mail from outside needs to be done by a mail fetch program, like the \masqmail\ internal \NAME{POP3} client or \name{fetchmail} for example. The configuration for \masqmail\ would be the same on every computer, except the hostname.
   1.144 -
   1.145 -For the same network but having a server, one could have \masqmail\ running on the server and using simple forwarders (see \ref{subsec:relay-only}) to the server on the workstations. This setup does only support mail transfer to the server, but not back to a workstation; also sending mail to another user on the same workstation is not possible.
   1.146 -
   1.147 -A better setup is to run \masqmail\ on every machine %FIXME
   1.148 -
   1.149 -
   1.150 -
   1.151 -
   1.152 -
   1.153 -
   1.154 -\subsection{When not to use \masqmail}
   1.155 -
   1.156 -...
   1.157 -
   1.158  
   1.159  
   1.160  
   1.161 @@ -214,6 +209,11 @@
   1.162  \subsubsection*{Online detection and routes}
   1.163  \label{sec:masqmail-routes}
   1.164  
   1.165 +\masqmail\ queues mail for destinations outside the local network if no connection to the internet is online. If the machine goes online, this mail is sent. Mail to local machines is sent immediately.
   1.166 +
   1.167 +\masqmail\ sends mail to local destinations, like users on the same machine and on other machines in the local net, immediately. Email to recipients outside the local net are queued when offline and sent when a online connection gets established.
   1.168 +
   1.169 +Further more does \masqmail\ respect online connections through different \NAME{ISP}s; a common thing for dial-up connections. In particular can different sender addresses be set, dependent on the \NAME{ISP} that is used. This prevents mail to be likely classified as spam.
   1.170  ---
   1.171  
   1.172  As \masqmail\ is focused on non-permanent Internet connections, online state can be queried by three methods: reading from a file, reading the output of a command, or by asking an \name{mserver}. Each method may return a string indicating one of the available routes being online, or returning nothing to indicate offline state.