1.1 --- a/thesis/tex/0-preface.tex	Tue Oct 14 11:48:47 2008 +0200
     1.2 +++ b/thesis/tex/0-preface.tex	Tue Oct 14 11:48:58 2008 +0200
     1.3 @@ -8,15 +8,21 @@
     1.4  
     1.5  
     1.6  \section*{Audience}
     1.7 -This document is targeted for \masqmail\ users and for people interested in mail systems in general. Security problems in electronic mail, \unix\ and the \NAME{C} programming language will also be discussed. Additional ones planning to take over an unmaintained software project will find real life experience in here.
     1.8 +This document is targeted for \masqmail\ users and for people interested in mail systems in general.
     1.9 +Security problems in electronic mail, \unix\ and the \NAME{C} programming language will also be discussed.
    1.10 +Additional ones planning to take over an unmaintained software project will find real life experience in here.
    1.11  
    1.12 -In each topic, basic knowledge is preconditioned. Nevertheless introductions are given and sources for further reading will be mentioned.
    1.13 +In each topic, basic knowledge is preconditioned.
    1.14 +Nevertheless introductions are given and sources for further reading will be mentioned.
    1.15  
    1.16 -This work focuses on the \unix\ operating system. Experience in usage, administration and program development is assumed. This includes the basic toolchain (e.g. \name{tar}, \name{grep}, etc.), user, file and permission management, as well as writing, compiling and installing programs written in the \NAME{C} language.
    1.17 +This work focuses on the \unix\ operating system.
    1.18 +Experience in usage, administration and program development is assumed.
    1.19 +This includes the basic toolchain (e.g.\ \name{tar}, \name{grep}, etc.), user, file and permission management, as well as writing, compiling and installing programs written in the \NAME{C} language.
    1.20  
    1.21  General information about \unix\ can be found in \cite{unixprogenv} %FIXME: references
    1.22  . %FIXME: references
    1.23 -explain about administrating \unix. And developing programs in \NAME{C} may be learned from \cite{cprog} and \cite{advunixprog}. %FIXME: references
    1.24 +explain about administrating \unix.
    1.25 +And developing programs in \NAME{C} may be learned from \cite{cprog} and \cite{advunixprog}. %FIXME: references
    1.26  
    1.27  %TODO: should I tell them to send email to me when having questions? Or somewhere else?
    1.28  

     2.1 --- a/thesis/tex/1-Introduction.tex	Tue Oct 14 11:48:47 2008 +0200
     2.2 +++ b/thesis/tex/1-Introduction.tex	Tue Oct 14 11:48:58 2008 +0200
     2.3 @@ -5,27 +5,40 @@
     2.4  %TODO: have a quote from Bell Labs about email here
     2.5  %FIXME: add references to text
     2.6  
     2.7 -Electronic mail (short: \name{email}) is a basic concept in \unix. On \unix\ machines, a lot of information is distributed by \name{system mail}, which is email sent by the operating system. Beside that, email is the common communication system between humans working on computers.
     2.8 +Electronic mail\index{electronic mail@electronic mail (email)} (short: \name{email}) is a basic concept in \unix.
     2.9 +On \unix\ machines, a lot of information is distributed by \name{system mail}, which is email sent by the operating system.
    2.10 +Beside that, email is the common communication system between humans working on computers.
    2.11  
    2.12 -The \unix\ operating system supports email since 1979 through the \name{mail user agent} (\NAME{MUA}) \path{/bin/mail}. For transporting mail in between two systems, the \NAME{UUCP} protocol (for ``\unix\ to \unix\ copy'') was invented.
    2.13 +The \unix\ operating system supports email since 1979 through the \name{mail user agent} (\NAME{MUA}) \path{/bin/mail}.
    2.14 +For transporting mail in between two systems, the \NAME{UUCP} protocol (for ``\unix\ to \unix\ copy'') was invented.
    2.15  %FIXME: what about `uuxqt' and `rmail'
    2.16  
    2.17 -As generally known, the early development of \unix\ was not only made in the \name{Bell Labratories} of \NAME{AT\&T}. But also the \name{Univerity of California at Berkeley} worked on their version of a \unix\ operating system, called \NAME{UCB} \unix, or \name{Berkeley} \unix.
    2.18 +As generally known, the early development of \unix\ was not only made in the \name{Bell Labratories} of \NAME{AT\&T}.
    2.19 +But also the \name{Univerity of California at Berkeley} worked on their version of a \unix\ operating system, called \NAME{UCB} \unix, or \name{Berkeley} \unix.
    2.20  
    2.21 -This lead to a second \NAME{MUA} from Berkeley: \name{Mail} (with a capital `M'). Also, no \NAME{UUCP} network was set up at Berkeley but an own creation called \name{BerkNet} was used.
    2.22 +This lead to a second \NAME{MUA} from Berkeley: \name{Mail} (with a capital `M').
    2.23 +Also, no \NAME{UUCP} network was set up at Berkeley but an own creation called \name{Berknet} was used.
    2.24  %FIXME: why? license issues? closed source?
    2.25  %TODO: what about `mailx'?
    2.26  
    2.27  Further more there was a third network type: the \NAME{ARPAnet}, based on the \name{transmission control protocol} (\NAME{TCP}).
    2.28  %FIXME: where did it came from?
    2.29  
    2.30 -Each of the three network types could transfer email between different machines. The file transfer itself was made using \NAME{FTP}, but the higher layered logic of the transfer was different in each. For example was the addressing schema not the same: \NAME{UUCP} used a flat-style schema, while \NAME{ARPAnet} was hierachical.
    2.31 +Each of the three network types could transfer email between different machines.
    2.32 +The file transfer itself was made using \NAME{FTP}, but the higher layered logic of the transfer was different in each.
    2.33 +For example was the addressing schema not the same: \NAME{UUCP} used a flat-style schema, while \NAME{ARPAnet} was hierachical.
    2.34  
    2.35 -Mail transport from one machine using one kind of network to a second machine using another kind was a problem. This showed up at Berkeley where some departments of the university had switched to \NAME{ARPAnet}, and some to \NAME{UUCP}, while the rest was \name{BerkNet}.
    2.36 +Mail transport from one machine using one kind of network to a second machine using another kind was a problem.
    2.37 +This showed up at Berkeley where some departments of the university had switched to \NAME{ARPAnet}, and some to \NAME{UUCP}, while the rest was \name{Berknet}.
    2.38  
    2.39 -It was around 1982, when Eric Allman, then a student at Berkeley, wrote \name{delivermail}. Its purpose was to transform email from one network to another. \name{delivermail} like its successor, the more flexible \sendmail, intermediated between the different networks. They were able to transform email messages from any network to any other.
    2.40 +It was around 1982, when Eric Allman, then a student at Berkeley, wrote \name{delivermail}.
    2.41 +Its purpose was to transform email from one network to another.
    2.42 +\name{delivermail} like its successor, the more flexible \sendmail, intermediated between the different networks.
    2.43 +They were able to transform email messages from any network to any other.
    2.44  
    2.45 -Todays email structure is basicly the same as then. The major difference is the uniformity of the underlying network, which is nearly always the \NAME{ARPAnet}-based \name{Internet}. Most other differences are organized as extensions to the old model of electronic mail.
    2.46 +Todays email structure is basicly the same as then.
    2.47 +The major difference is the uniformity of the underlying network, which is nearly always the \NAME{ARPAnet}-based \name{Internet}.
    2.48 +Most other differences are organized as extensions to the old model of electronic mail.
    2.49  
    2.50  More information about electronic mail and its history can be found at:
    2.51  %FIXME: add books and websites here
    2.52 @@ -35,7 +48,7 @@
    2.53  \section{Transporting mail}
    2.54  %TODO: include definitions from others here (cites)
    2.55  %TODO: when was the term ``mail transfer agent'' established?
    2.56 -The basic job of a \name{mail transfer agent} (or \name{mail transport agent}, short \NAME{MTA}) is to transfer/transport \name{electronic mail} (short \name{email}) from one host to another.
    2.57 +The basic job of a \name{mail transfer agent} (or \index{mail transport agent|see{mail transfer agent}}\name{mail transport agent}, short \NAME{MTA}) is to transfer/transport \name{electronic mail} (short \name{email}) from one host to another.
    2.58  
    2.59  
    2.60  
    2.61 @@ -47,7 +60,9 @@
    2.62  % FIXME: is that true?
    2.63  It was the first \NAME{MTA} and had no real alternative for a long time.
    2.64  
    2.65 -All other existing substitutes, which are mainly \name{postfix}, \name{exim}, \name{qmail} and the here regarded \name{masqmail}, mimic \name{sendmail}'s behavior. Especially, they all create a symbolic link named ``sendmail'' pointing to their own executable. This is because a lot of programs assume there is an executable called ``sendmail'' on every computer system.
    2.66 +All other existing substitutes, which are mainly \name{postfix}, \name{exim}, \name{qmail} and the here regarded \name{masqmail}, mimic \name{sendmail}'s behavior.
    2.67 +Especially, they all create a symbolic link named ``sendmail'' pointing to their own executable.
    2.68 +This is because a lot of programs assume there is an executable called ``sendmail'' on every computer system.
    2.69  
    2.70  Besides being the ``standard'', \name{sendmail} probably is the most scalable and powerful solution for transfering emails and definatly the most flexible one.
    2.71  

     3.1 --- a/thesis/tex/1-Masqmail.tex	Tue Oct 14 11:48:47 2008 +0200
     3.2 +++ b/thesis/tex/1-Masqmail.tex	Tue Oct 14 11:48:58 2008 +0200
     3.3 @@ -25,13 +25,26 @@
     3.4  %TODO: let oliver prove read it!
     3.5  %FIXME: add references
     3.6  
     3.7 -The date of the first release (version 0.0.1) is unknown. The only information available is, that it was packaged for \debian\ at 15\nth\ of September in 1999. Further releases were made every few weeks or month during 2000, 2001 and 2002. Development ended in mid-2003 in a hard stop. The last release known to me is version 0.2.20, released on 4\nth\ of June in 2003.
     3.8 +The date of the first release (version 0.0.1) is unknown.
     3.9 +The only information available is, that it was packaged for \debian\ at 15\nth\ of September in 1999.
    3.10 +Further releases were made every few weeks or month during 2000, 2001 and 2002.
    3.11 +Development ended in mid-2003 in a hard stop.
    3.12 +The last release known to me is version 0.2.20, released on 4\nth\ of June in 2003.
    3.13  
    3.14 -During the time of development, Oliver released 53 versions. That means a new release in less than every 20 days in average!
    3.15 +During the time of development, Oliver released 53 versions.
    3.16 +That means a new release in less than every 20 days in average!
    3.17  
    3.18  Mentionable are the four \emph{beta} releases of version 0.1.8 (named with the trailing letters `a' to `d') in winter 2000/2001 and the security-fix 0.1.15.1 in 2002.
    3.19  
    3.20 -One extra release (version 0.2.21) was made by him in November 2005. This one is only available from the \debian\ pool. Comparing it to version 0.2.20 shows, that no source code was altered. Only building documents (like Makefiles) and \debian\ packageing documents were changed. That leeds to the assumption that this last release was specificly created for the needs of \debian---to fix some errors in the package.
    3.21 +One extra release (version 0.2.21) was made by him in November 2005.
    3.22 +This one is only available from the \debian\ pool.
    3.23 +Comparing it to version 0.2.20 shows, that no source code was altered.
    3.24 +Only building documents (like Makefiles) and \debian\ packageing documents were changed.
    3.25 +That leeds to the assumption that this last release was specificly created for the needs of \debian---to fix some errors in the package.
    3.26  
    3.27 -In May 2000 the minor version number increased to `1'. Nothing special is mentioned in the documentation about that. When it increased again to start the 0.2.x releases, Oliver titled them as the ``development branch'' of \masqmail. At that second time, he started developing the 0.2.x ``development branch'', continuing to work on the 0.1.x series. His parallel work on both branches lasted for four month, and one additional last release, numbered 0.1.17, one more year later.
    3.28 +In May 2000 the minor version number increased to `1'.
    3.29 +Nothing special is mentioned in the documentation about that.
    3.30 +When it increased again to start the 0.2.x releases, Oliver titled them as the ``development branch'' of \masqmail.
    3.31 +At that second time, he started developing the 0.2.x ``development branch'', continuing to work on the 0.1.x series.
    3.32 +His parallel work on both branches lasted for four month, and one additional last release, numbered 0.1.17, one more year later.
    3.33  

     4.1 --- a/thesis/tex/2-FreeSoftwareProjects.tex	Tue Oct 14 11:48:47 2008 +0200
     4.2 +++ b/thesis/tex/2-FreeSoftwareProjects.tex	Tue Oct 14 11:48:58 2008 +0200
     4.3 @@ -4,7 +4,7 @@
     4.4  To understand \freesw\ projects, one needs to understand \freesw\ itself first.
     4.5  
     4.6  \section{About \freesw}
     4.7 -The term ``Free Software'' was coined by the \name{Free Software Foundation} (short: \NAME{FSF}), founded by Richard~M.~Stallman (known as ``RMS'') in 1985. %FIXME: check date
     4.8 +The term ``Free Software'' was coined by the \name{Free Software Foundation} (short: \NAME{FSF}), founded by Richard M.\ Stallman (known as ``RMS'') in 1985. %FIXME: check date
     4.9  Although various licenses make software free, none of them represents the thinking of \freesw\ like the the \GNU\ \gpl\ (short: \GPL), which was written by Stallman in 1983.
    4.10  One could say, the \GPL\ ``powered'' the \name{Free Software movement}.
    4.11  
    4.12 @@ -45,7 +45,7 @@
    4.13  
    4.14  The other, now less common, method is a more closed group, developing in a ``sealed'' room, but releasing finished versions to the public.
    4.15  
    4.16 -Eric~S.~Raymond discusses about these methods, which he named \name{the bazaar} and \name{the cathedral}. %FIXME: add reference
    4.17 +Eric S.\ Raymond discusses about these methods, which he named \name{the bazaar} and \name{the cathedral}. %FIXME: add reference
    4.18  
    4.19  The following text will focus on the ``bazaar'' model.
    4.20  

     5.1 --- a/thesis/tex/3-General.tex	Tue Oct 14 11:48:47 2008 +0200
     5.2 +++ b/thesis/tex/3-General.tex	Tue Oct 14 11:48:58 2008 +0200
     5.3 @@ -1,5 +1,5 @@
     5.4  \chapter{In general}
     5.5 -\section{Problems of email}
     5.6 +\section{Problems of electronic mail}
     5.7  \section{Problems of \unix/\NAME{C}}
     5.8  \section{Problems of \MTA{}s}
     5.9  

     6.1 --- a/thesis/tex/titlepage.tex	Tue Oct 14 11:48:47 2008 +0200
     6.2 +++ b/thesis/tex/titlepage.tex	Tue Oct 14 11:48:58 2008 +0200
     6.3 @@ -12,18 +12,20 @@
     6.4  \section*{\centering Abstract}
     6.5  \masqmail\ is a \mta\ for workstations and small networks. It is a drop-in replacement for \sendmail, but much smaller.
     6.6  
     6.7 -This diploma thesis analyzes the structure and concepts of \masqmail, and its security and safety. Based on this knowledge, the source code will get improved and everything will be written down for documentation.
     6.8 +This diploma thesis analyzes the structure and concepts of \masqmail, and its security and safety.
     6.9 +Based on this knowledge, the source code will get improved and everything will be written down for documentation.
    6.10  
    6.11  After successful tests in a real environment, a new version of \masqmail\ will be released and it will be packaged for the \gnulinux\ Distribution \debian.
    6.12  
    6.13  \vspace*{12ex}
    6.14  
    6.15 -Diploma thesis of Markus \textsc{Schnalke} (matriculation number: 039131).\\
    6.16 -Course \name{Business Information Systems} at the \name{University of Applied Sciences Ulm}.\\
    6.17 +{\bfseries Diploma thesis} of Markus \textsc{Schnalke} (matriculation number: 039131).\\
    6.18 +Course \emph{Business Information Systems} at the \emph{University of Applied Sciences Ulm}.\\
    6.19  Year 2009.
    6.20  
    6.21 +\medskip
    6.22  Supervisor:\\
    6.23 -Prof.~Dr.~rer.~nat. Markus \textsc{Schäffter}, \name{University of Applied Sciences Ulm}.
    6.24 +Prof.\ Dr.\ rer.\ nat.\ Markus \textsc{Schäffter}, \emph{University of Applied Sciences Ulm}.
    6.25  
    6.26  \vfill
    6.27