| rev |
line source |
|
meillo@15
|
1 \chapter{About \name{mail transfer agent}s}
|
|
meillo@15
|
2
|
|
meillo@15
|
3 % TODO: describe content of this chapter here
|
|
meillo@15
|
4
|
|
meillo@15
|
5
|
|
meillo@15
|
6 \section{What is a \name{mail transfer agent}?}
|
|
meillo@15
|
7 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.
|
|
meillo@15
|
8
|
|
meillo@15
|
9 % TODO: include definitions from others here (cites)
|
|
meillo@15
|
10
|
|
meillo@15
|
11
|
|
meillo@15
|
12 \section{History of \NAME{MTA}s}
|
|
meillo@15
|
13 % FIXME: is that true?
|
|
meillo@15
|
14 In the old days, the 70s, when Unix was created, computers were expensive. Universities and big firms normally had a single server with an amount of terminals connected to it. The computer filled a whole room somewhere in the cellar. People were operating at the terminals that were located in the offices and wired to the server. At that time, there was hardly no networking at all.
|
|
meillo@15
|
15
|
|
meillo@15
|
16 During the following years, when computers became affordable and so more common (but still no personal computers at that time), connections between single computers were established. Inter-university connections were one of the first networks.
|
|
meillo@15
|
17
|
|
meillo@15
|
18 Electronic mail is a basic concept in Unix. A lot of information gets distributed via system mail on Unix machines. System mail is electronic mail that stays on one machine. In nowadays this is primary notifications from system programs. But back then, there were frequently sent emails between users on the same machine.
|
|
meillo@15
|
19
|
|
meillo@15
|
20 When computers were connected to each other and networks grew, the need appered to send electronic mail from one machine to another. E.g. Alice sitting on a terminal connected to server1 wants to send email to Bob sitting on a terminal connected to server2.
|
|
meillo@15
|
21
|
|
meillo@15
|
22 Unix provided everything for that task, except a good tool to do the mail transport from server1 to server2.
|
|
meillo@15
|
23
|
|
meillo@15
|
24 At that point the fathers of Unix at \name{Bell Labs} wrote the \NAME{UUCP} program and its compagnons. At about the same time in Berkeley a different solution for the same problem was developed: Eric Allman wrote \name{sendmail}.\footnote{To be exact: He wrote \name{delivermail} which he enhanced to \name{sendmail}.}
|
|
meillo@15
|
25
|
|
meillo@15
|
26
|
|
meillo@15
|
27 \section{About \name{sendmail}}
|
|
meillo@15
|
28 \name{sendmail} is the defacto-standard for \name{mail transfer agents}.
|
|
meillo@15
|
29
|
|
meillo@15
|
30 % FIXME: is that true?
|
|
meillo@15
|
31 It was the first \NAME{MTA} and had no real alternative for a long time.
|
|
meillo@15
|
32
|
|
meillo@15
|
33 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.
|
|
meillo@15
|
34
|
|
meillo@15
|
35 Besides being the ``standard'', \name{sendmail} probably is the most scalable and powerful solution for transfering emails and definatly the most flexible one.
|
