Mercurial > docs > diploma
annotate thesis/tex/1-Introduction.tex @ 50:f944ca6dd688
added CATB cite; added unbreakable spaces
author | meillo@marmaro.de |
---|---|
date | Tue, 14 Oct 2008 21:59:22 +0200 |
parents | d52fa2350137 |
children | 56fd50f9bbf3 |
rev | line source |
---|---|
26
fb9ba63f6957
changed to new thesis structure; moved text pieces away; updated project plan
meillo@marmaro.de
parents:
diff
changeset
|
1 \chapter{Introduction} |
42 | 2 \label{chap:introduction} |
26
fb9ba63f6957
changed to new thesis structure; moved text pieces away; updated project plan
meillo@marmaro.de
parents:
diff
changeset
|
3 |
fb9ba63f6957
changed to new thesis structure; moved text pieces away; updated project plan
meillo@marmaro.de
parents:
diff
changeset
|
4 \section{History of electronic mail} |
30 | 5 %TODO: have a quote from Bell Labs about email here |
6 %FIXME: add references to text | |
7 | |
47 | 8 Electronic mail\index{electronic mail@electronic mail (email)} (short: \name{email}) is a basic concept in \unix. |
9 On \unix\ machines, a lot of information is distributed by \name{system mail}, which is email sent by the operating system. | |
10 Beside that, email is the common communication system between humans working on computers. | |
27 | 11 |
47 | 12 The \unix\ operating system supports email since 1979 through the \name{mail user agent} (\NAME{MUA}) \path{/bin/mail}. |
13 For transporting mail in between two systems, the \NAME{UUCP} protocol (for ``\unix\ to \unix\ copy'') was invented. | |
30 | 14 %FIXME: what about `uuxqt' and `rmail' |
15 | |
47 | 16 As generally known, the early development of \unix\ was not only made in the \name{Bell Labratories} of \NAME{AT\&T}. |
17 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. | |
30 | 18 |
47 | 19 This lead to a second \NAME{MUA} from Berkeley: \name{Mail} (with a capital `M'). |
20 Also, no \NAME{UUCP} network was set up at Berkeley but an own creation called \name{Berknet} was used. | |
30 | 21 %FIXME: why? license issues? closed source? |
31 | 22 %TODO: what about `mailx'? |
27 | 23 |
30 | 24 Further more there was a third network type: the \NAME{ARPAnet}, based on the \name{transmission control protocol} (\NAME{TCP}). |
25 %FIXME: where did it came from? | |
27 | 26 |
47 | 27 Each of the three network types could transfer email between different machines. |
28 The file transfer itself was made using \NAME{FTP}, but the higher layered logic of the transfer was different in each. | |
29 For example was the addressing schema not the same: \NAME{UUCP} used a flat-style schema, while \NAME{ARPAnet} was hierachical. | |
30 | 30 |
47 | 31 Mail transport from one machine using one kind of network to a second machine using another kind was a problem. |
32 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}. | |
27 | 33 |
47 | 34 It was around 1982, when Eric Allman, then a student at Berkeley, wrote \name{delivermail}. |
35 Its purpose was to transform email from one network to another. | |
36 \name{delivermail} like its successor, the more flexible \sendmail, intermediated between the different networks. | |
37 They were able to transform email messages from any network to any other. | |
30 | 38 |
47 | 39 Todays email structure is basicly the same as then. |
40 The major difference is the uniformity of the underlying network, which is nearly always the \NAME{ARPAnet}-based \name{Internet}. | |
41 Most other differences are organized as extensions to the old model of electronic mail. | |
27 | 42 |
30 | 43 More information about electronic mail and its history can be found at: |
44 %FIXME: add books and websites here | |
45 | |
27 | 46 |
26
fb9ba63f6957
changed to new thesis structure; moved text pieces away; updated project plan
meillo@marmaro.de
parents:
diff
changeset
|
47 |
fb9ba63f6957
changed to new thesis structure; moved text pieces away; updated project plan
meillo@marmaro.de
parents:
diff
changeset
|
48 \section{Transporting mail} |
31 | 49 %TODO: include definitions from others here (cites) |
50 %TODO: when was the term ``mail transfer agent'' established? | |
47 | 51 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. |
27 | 52 |
53 | |
26
fb9ba63f6957
changed to new thesis structure; moved text pieces away; updated project plan
meillo@marmaro.de
parents:
diff
changeset
|
54 |
30 | 55 |
34 | 56 \section{\sendmail} |
42 | 57 \label{sec:sendmail} |
31 | 58 \name{sendmail} is the de facto standard for \name{mail transfer agents}. |
27 | 59 |
60 % FIXME: is that true? | |
61 It was the first \NAME{MTA} and had no real alternative for a long time. | |
62 | |
47 | 63 All other existing substitutes, which are mainly \name{postfix}, \name{exim}, \name{qmail} and the here regarded \name{masqmail}, mimic \name{sendmail}'s behavior. |
64 Especially, they all create a symbolic link named ``sendmail'' pointing to their own executable. | |
65 This is because a lot of programs assume there is an executable called ``sendmail'' on every computer system. | |
27 | 66 |
67 Besides being the ``standard'', \name{sendmail} probably is the most scalable and powerful solution for transfering emails and definatly the most flexible one. | |
68 | |
26
fb9ba63f6957
changed to new thesis structure; moved text pieces away; updated project plan
meillo@marmaro.de
parents:
diff
changeset
|
69 |
30 | 70 |
26
fb9ba63f6957
changed to new thesis structure; moved text pieces away; updated project plan
meillo@marmaro.de
parents:
diff
changeset
|
71 \section{(a look at Windows)} |
fb9ba63f6957
changed to new thesis structure; moved text pieces away; updated project plan
meillo@marmaro.de
parents:
diff
changeset
|
72 |