1.1 --- a/thesis/tex/1-Introduction.tex	Tue Oct 14 11:48:47 2008 +0200
     1.2 +++ b/thesis/tex/1-Introduction.tex	Tue Oct 14 11:48:58 2008 +0200
     1.3 @@ -5,27 +5,40 @@
     1.4  %TODO: have a quote from Bell Labs about email here
     1.5  %FIXME: add references to text
     1.6  
     1.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.
     1.8 +Electronic mail\index{electronic mail@electronic mail (email)} (short: \name{email}) is a basic concept in \unix.
     1.9 +On \unix\ machines, a lot of information is distributed by \name{system mail}, which is email sent by the operating system.
    1.10 +Beside that, email is the common communication system between humans working on computers.
    1.11  
    1.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.
    1.13 +The \unix\ operating system supports email since 1979 through the \name{mail user agent} (\NAME{MUA}) \path{/bin/mail}.
    1.14 +For transporting mail in between two systems, the \NAME{UUCP} protocol (for ``\unix\ to \unix\ copy'') was invented.
    1.15  %FIXME: what about `uuxqt' and `rmail'
    1.16  
    1.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.
    1.18 +As generally known, the early development of \unix\ was not only made in the \name{Bell Labratories} of \NAME{AT\&T}.
    1.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.
    1.20  
    1.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.
    1.22 +This lead to a second \NAME{MUA} from Berkeley: \name{Mail} (with a capital `M').
    1.23 +Also, no \NAME{UUCP} network was set up at Berkeley but an own creation called \name{Berknet} was used.
    1.24  %FIXME: why? license issues? closed source?
    1.25  %TODO: what about `mailx'?
    1.26  
    1.27  Further more there was a third network type: the \NAME{ARPAnet}, based on the \name{transmission control protocol} (\NAME{TCP}).
    1.28  %FIXME: where did it came from?
    1.29  
    1.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.
    1.31 +Each of the three network types could transfer email between different machines.
    1.32 +The file transfer itself was made using \NAME{FTP}, but the higher layered logic of the transfer was different in each.
    1.33 +For example was the addressing schema not the same: \NAME{UUCP} used a flat-style schema, while \NAME{ARPAnet} was hierachical.
    1.34  
    1.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}.
    1.36 +Mail transport from one machine using one kind of network to a second machine using another kind was a problem.
    1.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}.
    1.38  
    1.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.
    1.40 +It was around 1982, when Eric Allman, then a student at Berkeley, wrote \name{delivermail}.
    1.41 +Its purpose was to transform email from one network to another.
    1.42 +\name{delivermail} like its successor, the more flexible \sendmail, intermediated between the different networks.
    1.43 +They were able to transform email messages from any network to any other.
    1.44  
    1.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.
    1.46 +Todays email structure is basicly the same as then.
    1.47 +The major difference is the uniformity of the underlying network, which is nearly always the \NAME{ARPAnet}-based \name{Internet}.
    1.48 +Most other differences are organized as extensions to the old model of electronic mail.
    1.49  
    1.50  More information about electronic mail and its history can be found at:
    1.51  %FIXME: add books and websites here
    1.52 @@ -35,7 +48,7 @@
    1.53  \section{Transporting mail}
    1.54  %TODO: include definitions from others here (cites)
    1.55  %TODO: when was the term ``mail transfer agent'' established?
    1.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.
    1.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.
    1.58  
    1.59  
    1.60  
    1.61 @@ -47,7 +60,9 @@
    1.62  % FIXME: is that true?
    1.63  It was the first \NAME{MTA} and had no real alternative for a long time.
    1.64  
    1.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.
    1.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.
    1.67 +Especially, they all create a symbolic link named ``sendmail'' pointing to their own executable.
    1.68 +This is because a lot of programs assume there is an executable called ``sendmail'' on every computer system.
    1.69  
    1.70  Besides being the ``standard'', \name{sendmail} probably is the most scalable and powerful solution for transfering emails and definatly the most flexible one.
    1.71