1 \chapter{Introduction}

2 \label{chap:introduction}

3

4 \section{History of electronic mail}

5 %TODO: have a quote from Bell Labs about email here

6 %FIXME: add references to text

7

8 Electronic mail\index{electronic mail} (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.

11

12 The \unix\ operating system supports email through the \name{mail user agent} (\NAME{MUA}) \name{/bin/mail}.

13

14 As generally known, development of \unix\ was not only made in the \name{Bell Labratories} of \NAME{AT\&T}.

15 The \name{Univerity of California at Berkeley} worked on their version of a \unix\ operating system, too.

16 It is refered to as \NAME{UCB} \unix, or \name{Berkeley} \unix\index{Berkeley Unix}.

17

18 The few features of \name{/bin/mail} lead to a second \NAME{MUA} from Berkeley: \name{Mail} (with a capital `M').

19 Later, the superior functionality of \name{Mail} went back to \name{Bell Labs} and into the program \name{mailx}, the successor of \name{/bin/mail}.

20 The different programs for handling mail are a good example for the problem of standardization of \unix.

21

22 Nowadays, \name{mailx} and \name{Mail} are quite equivalent and \name{/bin/mail} is linked to either of them---whichever is installed.

23

24 For transporting mail in between two systems, the \NAME{UUCP} program and protocol suite (for ``\unix\ to \unix\ copy'') was invented at \name{Bell Labs}.

25 Berkeley however had an own creation called \name{Berknet} in use. %FIXME: why? license issues? closed source?

26 Further more there was a third important network type: the \NAME{ARPAnet}, based on the \name{transmission control protocol} (\NAME{TCP}). %FIXME: where did it came from?

27

28 Each of the three network types could transfer email between different machines.

29 The file transfer itself was made using \NAME{FTP}, but the higher layered logic of the transfer was different in each.

30 For example was the addressing schema not the same: \NAME{UUCP} used a flat-style schema, while \NAME{ARPAnet} was hierachical.

31

32 Mail transport from one machine using one kind of network to a second machine using another kind was a problem.

33 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}.

34

35 It was around 1982, when Eric Allman, then a student at Berkeley, wrote \name{delivermail}.

36 Its purpose was to transform email from one network to another.

37 \name{delivermail} like its successor, the more flexible \sendmail, intermediated between the different networks.

38 They were able to transform email messages from any network to any other.

39

40 Todays email structure is basicly the same as then.

41 The major difference is the uniformity of the underlying network, which is nearly always the \NAME{ARPAnet}-based \name{Internet}.

42 Most other differences are organized as extensions to the old model of electronic mail.

43

44 More information about electronic mail and its history can be found at:

45 %FIXME: add books and websites here

46

47 % http://www.helpdesk.umd.edu/documents/4/4804/

48 % http://www.networkcomputing.com/unixworld/tutorial/810.txt.html

49 % http://www.livinginternet.com/i/iw_unix_war.htm

50 % http://www.nobell.org/~gjm/about/ihnp4.html

51 % http://en.wikipedia.org/wiki/E-mail

52 % http://en.wikipedia.org/wiki/UUCP

53 % http://en.wikipedia.org/wiki/ARPAnet

54 % http://en.wikipedia.org/wiki/History_of_the_Internet

55 % http://www.multicians.org/thvv/mail-history.html

56 % http://openmap.bbn.com/~tomlinso/ray/firstemailframe.html

57 % http://www.livinginternet.com/e/ei.htm

58 % http://www.cs.ucsb.edu/~almeroth/classes/F04.176A/homework1_good_papers/jay-akkad.html

59

60

61 \section{Transporting mail}

62 %TODO: include definitions from others here (cites)

63 %TODO: when was the term ``mail transfer agent'' established?

64 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.

65

66 Here are definitions from various sources:

67

68 \begin{quotation}

69 A mail transfer agent (MTA) is a highly specialized program that delivers mail and transports it between machines, like the post office. Usually there is only one MTA on a machine. The sendmail program is an MTA.

70 \cite{sendmail}

71 \end{quotation}

72

73 \begin{quotation}

74 A mail transfer agent (MTA) (also called a mail transport agent, message transfer agent, or smtpd (short for SMTP daemon)), is a computer program or software agent that transfers electronic mail messages from one computer to another.

75 \citeweb{wikipedia:mta}

76 \end{quotation}

77

78 \begin{quotation}

79 mail server (also known as a mail transfer agent or MTA, a mail transport agent, a mail router or an Internet mailer) is an application that receives incoming e-mail from local users (people within the same domain) and remote senders and forwards outgoing e-mail for delivery.

80 \citeweb{website:techtarget}

81 \end{quotation}

82

83 \begin{quotation}

84 Message Transfer Agent - (MTA, Mail Transfer Agent) Any program responsible for delivering e-mail messages. Upon receiving a message from a Mail User Agent or another MTA, often by SMTP over the Internet, it stores it temporarily locally and analyses the recipients and delivers it to any local addressees and/or forwards it to other remote MTAs (routing) for delivery to remote recipients. In either case it may edit and/or add to the message headers.

85

86 The most widely used MTA for Unix is sendmail, which communicates using SMTP.

87

88 RFC 2821 (SMTP) expands MTA as ``Mail Transfer Agent'' though this is less common. Alternatives with ``Transport'' are also seen but less correct.

89 \citeweb{website:thefreedictionary}

90 \end{quotation}

91

92 \begin{quotation}

93 mail transfer agent (MTA) The program responsible for delivering e-mail messages. Upon receiving a message from a mail user agent or another MTA it stores it temporarily locally and analyses the recipients and either delivers it (local addressee) or forwards it to another MTA. In either case it may edit and/or add to the message headers. A widely used MTA for Unix is sendmail.

94 \citeweb{website:faqs}

95 \end{quotation}

96

97 \begin{quotation}

98 Mail Transfer Agent (MTA): The means by which mail messages are transferred between machines over the Internet.

99 \citeweb{website:freeserve.co.uk}

100 \end{quotation}

101

102

103 \section{\sendmail}

104 \label{sec:sendmail}

105 \name{sendmail} is the de facto standard for \name{mail transfer agents}.

106

107 % FIXME: is that true?

108 It was the first \NAME{MTA} and had no real alternative for a long time.

109

110 Most other existing substitutes (on \unix\ systems), which are mainly \name{postfix}, \name{exim}, \name{qmail} and the here regarded \name{masqmail}, mimic \name{sendmail}'s interface.

111 Especially, they all create a symbolic link named ``sendmail'' pointing to their own executable.

112 This is because a lot of programs assume there is an executable called ``sendmail'' on every computer system existing.

113

114 Besides being the ``standard'', \name{sendmail} probably is the most scalable and powerful solution for transfering emails and definately the most flexible one.

115

116

117

118 \section{(a look at Windows)}

119