Mercurial > docs > diploma

comparison thesis/tex/1-Introduction.tex @ 31:2a191e20b4aa

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
minor stuff
author meillo@marmaro.de
date Tue, 07 Oct 2008 14:44:22 +0200
parents 6c4b50b44d05
children f789b659f094
comparison
equal deleted inserted replaced
30:6c4b50b44d05 31:2a191e20b4aa
11 11
12 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. 12 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.
13 13
14 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. 14 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.
15 %FIXME: why? license issues? closed source? 15 %FIXME: why? license issues? closed source?
16 %TODO: what about `mailx'?
16 17
17 Further more there was a third network type: the \NAME{ARPAnet}, based on the \name{transmission control protocol} (\NAME{TCP}). 18 Further more there was a third network type: the \NAME{ARPAnet}, based on the \name{transmission control protocol} (\NAME{TCP}).
18 %FIXME: where did it came from? 19 %FIXME: where did it came from?
19 20
20 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. 21 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.
29 %FIXME: add books and websites here 30 %FIXME: add books and websites here
30 31
31 32
32 33
33 \section{Transporting mail} 34 \section{Transporting mail}
35 %TODO: include definitions from others here (cites)
36 %TODO: when was the term ``mail transfer agent'' established?
34 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. 37 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.
35 38
36 % TODO: include definitions from others here (cites)
37 39
38 40
39 41
40 \section{sendmail} 42 \section{sendmail}
41 \name{sendmail} is the defacto-standard for \name{mail transfer agents}. 43 \name{sendmail} is the de facto standard for \name{mail transfer agents}.
42 44
43 % FIXME: is that true? 45 % FIXME: is that true?
44 It was the first \NAME{MTA} and had no real alternative for a long time. 46 It was the first \NAME{MTA} and had no real alternative for a long time.
45 47
46 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. 48 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.