1.1 --- a/thesis/tex/1-Introduction.tex	Thu Dec 11 17:37:56 2008 +0100
     1.2 +++ b/thesis/tex/1-Introduction.tex	Mon Dec 15 13:39:46 2008 +0100
     1.3 @@ -14,7 +14,7 @@
     1.4  
     1.5  (include history of email, definition of MTA and sendmail-compatibility in text)
     1.6  
     1.7 -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.8 +The \masqmail\ program was written by Oliver \person{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.9  
    1.10  \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.11  
    1.12 @@ -26,7 +26,7 @@
    1.13  
    1.14  
    1.15  \subsubsection{Target field}
    1.16 -Its original author, \person{Oliver Kurth}, sees \masqmail\ so:
    1.17 +Its original author, Oliver \person{Kurth}, sees \masqmail\ so:
    1.18  \begin{quote}
    1.19  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.20  \end{quote}

     2.1 --- a/thesis/tex/2-MarketAnalysis.tex	Thu Dec 11 17:37:56 2008 +0100
     2.2 +++ b/thesis/tex/2-MarketAnalysis.tex	Mon Dec 15 13:39:46 2008 +0100
     2.3 @@ -98,7 +98,7 @@
     2.4  \subsubsection*{Unified Communication}
     2.5  \name{Unified communication} is the technology aiming to consolidate and integrate all electronic communication and providing access for all kinds of hardware clients. Unified communication tries to bring the tree trends here mentioned together. The \name{{\smaller PC} Magazine} has the following definition in its Encyclopedia \citeweb{pcmag:uc}: ``[Unified communications is] The real-time redirection of a voice, text or e-mail message to the device closest to the intended recipient at any given time.'' The main goal is to integrate all kinds of communication (asynchronous and synchronous) into one system, hence this requires real-time delivery of data.
     2.6  
     2.7 -According to \person{Michael Osterman} \citeweb{howto-def-uc}, unified communications is already possible as far as various incoming sources are routed to one storage where messages can be accessed by one or a few clients. But a system with an ``intelligent parser of a single data stream into separate streams that are designed to meet the real-time needs of the user'' is a goal for the future, he says.
     2.8 +According to Michael \person{Osterman} \citeweb{howto-def-uc}, unified communications is already possible as far as various incoming sources are routed to one storage where messages can be accessed by one or a few clients. But a system with an ``intelligent parser of a single data stream into separate streams that are designed to meet the real-time needs of the user'' is a goal for the future, he says.
     2.9  
    2.10  The question is, if the integration of synchronous and asynchronous message transfer does make sense. A communication between one person talking on the phone and the other replying using his instant messenger, certainly does, if the text-to-speech and speech-to-text converting is fast and the quality good enough. But transferring large video messages and real-time communication data with the same technology, possibly does not.
    2.11  
    2.12 @@ -191,7 +191,7 @@
    2.13  
    2.14  \subsubsection*{New email protocols}
    2.15  
    2.16 -Another concept to redesign the electronic mail system, but this time focused on mail transfer is named ``Internet Mail 2000''. It was proposed by \person{Daniel~J.\ Bernstein}, the creator of \qmail. Similar approaches were independently introduced by others too.
    2.17 +Another concept to redesign the electronic mail system, but this time focused on mail transfer is named ``Internet Mail 2000''. It was proposed by \person{Daniel~J.\ }{Bernstein}, the creator of \qmail. Similar approaches were independently introduced by others too.
    2.18  
    2.19  As main change it makes the sender have the responsibility of mail storage; only a notification about a mail message gets send to the receiver, who can fetch the message then from the sender's server. This is in contrast to the \NAME{SMTP} mail architecture, where mail and the responsibility for it is transferred from the sender to the receiver.
    2.20  

     3.1 --- a/thesis/tex/4-MasqmailsFuture.tex	Thu Dec 11 17:37:56 2008 +0100
     3.2 +++ b/thesis/tex/4-MasqmailsFuture.tex	Mon Dec 15 13:39:46 2008 +0100
     3.3 @@ -1,15 +1,18 @@
     3.4  \chapter{\masqmail's present and future}
     3.5  
     3.6  \section{Existing code base}
     3.7 -Here regarded is version 0.2.21 of \masqmail. This is the last version released by \person{Oliver Kurth}, and the basis for my thesis.
     3.8 +Here regarded is version 0.2.21 of \masqmail. This is the last version released by Oliver \person{Kurth}, and the basis for my thesis.
     3.9 +
    3.10  
    3.11  \subsubsection*{Features}
    3.12  
    3.13 -\masqmail\ accepts mail on the command line and via \SMTP. Mail queueing and alias expansion is supported. \masqmail\ is able to deliver mail to local mailboxes (in \name{mbox} or \name{maildir} format) or pass it to a \name{mail delivery agent} (like \name{procmail}). Mail destinated to remote locations is sent using \SMTP.
    3.14 +\masqmail\ accepts mail on the command line and via \SMTP. Mail queueing and alias expansion is supported. \masqmail\ is able to deliver mail to local mailboxes (in \name{mbox} or \name{maildir} format) or pass it to a \name{mail delivery agent} (like \name{procmail}). Mail destinated to remote locations is sent using \SMTP\ or can be piped to commands, being gatesways to \NAME{UUCP} or \NAME{FAX} for example.
    3.15  
    3.16 -Outgoing \SMTP\ connections feature \SMTP-\NAME{AUTH} and \SMTP-after-\NAME{POP} authentication, but incoming \SMTP\ does not.
    3.17 +Outgoing \SMTP\ connections feature \SMTP-\NAME{AUTH} and \SMTP-after-\NAME{POP} authentication, but incoming connections do not. Using wrappers for outgoing connections is supported. This offers a two way communication through a wrapper application like \name{openssl}.
    3.18  %todo: what about SSL/TLS encryption?
    3.19  
    3.20 +\masqmail\ focuses on non-permanent online connections, thus a concept of online routes is used. One may configure any amount of routes to send mail. Each route can have criterias, like matching \texttt{From:} or \texttt{To:} headers, to determine if mail is allowed to be sent using it. Mail to destinations outside the local net gets queued until \masqmail\ is informed about the existance of a online connection.
    3.21 +
    3.22  The \masqmail\ executable can be called under various names for sendmail-compatibility reasons. This is organized by symbolic links with different names pointing to the \masqmail\ executable. The \sendmail\ names are \path{/usr/lib/sendmail} and \path{/usr/sbin/sendmail} because many programs expect the \mta\ to be located there. Further more \sendmail\ supports calling it with a different name instead of supplying command line arguments. The best known of this shortcuts is \path{mailq}, which is equivilent to calling it with the argument \verb+-bq+. \masqmail\ recognizes the names \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 name \path{newaliases} because \masqmail\ does not generate binary representations of the alias file.\footnote{A shell script located named \path{newaliases}, that invokes \texttt{masqmail -bi}, can provide the command to satisfy other software needing it.} \path{hoststat} and \path{purgestat} are missing for sendmail-compatibility.
    3.23  %masqmail: mailq, mailrm, runq, rmail, smtpd/in.smtpd
    3.24  %sendmail: hoststat, mailq, newaliases, purgestat, smtpd