Mercurial > docs > master
comparison ch03.roff @ 105:9ff356d84c57
Added reference to Allman to the text; added missing reference to ML.
author | markus schnalke <meillo@marmaro.de> |
---|---|
date | Thu, 21 Jun 2012 08:58:56 +0200 |
parents | 2818ca27d24c |
children |
comparison
equal
deleted
inserted
replaced
104:2818ca27d24c | 105:9ff356d84c57 |
---|---|
59 agents, mmh is a MUA only. | 59 agents, mmh is a MUA only. |
60 This general difference initiated the development of mmh. | 60 This general difference initiated the development of mmh. |
61 Removing the mail transfer facilities had been the first work task | 61 Removing the mail transfer facilities had been the first work task |
62 in the mmh project. | 62 in the mmh project. |
63 .P | 63 .P |
64 The Mail Submission Agent (MSA) is called | 64 Focusing on one mail agent role only is motivated by Eric Allman's |
65 \fIMessage Transfer Service\fP (MTS) in nmh. | 65 experience with Sendmail. |
66 The facility established network connections and spoke SMTP to submit | 66 He identified limiting Sendmail the MTA task had be one reason for |
67 its success: | |
68 .[ [ | |
69 costales sendmail | |
70 .], p. xviii] | |
71 .QS | |
72 Second, I limited myself to the routing function \(en | |
73 I wouldn't write user agents or delivery backends. | |
74 This was a departure of the dominant through of the time, | |
75 in which routing logic, local delivery, and often the network code | |
76 were incorporated directly into the user agents. | |
77 .QE | |
78 .P | |
79 In mmh, the Mail Submission Agent (MSA) is called | |
80 \fIMessage Transfer Service\fP (MTS). | |
81 This facility, implemented by the | |
82 .Pn post | |
83 command, established network connections and spoke SMTP to submit | |
67 messages for relay to the outside world. | 84 messages for relay to the outside world. |
68 This part was implemented by the | 85 The changes in email demanded changes in this part of nmh too. |
69 .Pn post | |
70 command. | |
71 The changes in email in the last years | |
72 demanded changes in this part of nmh too. | |
73 Encryption and authentication for network connections | 86 Encryption and authentication for network connections |
74 needed to be supported, hence TLS and SASL were introduced into nmh. | 87 needed to be supported, hence TLS and SASL were introduced into nmh. |
75 This added complexity to nmh without improving it in its core functions. | 88 This added complexity to nmh without improving it in its core functions. |
76 Also, keeping up with recent developments in the field of | 89 Also, keeping up with recent developments in the field of |
77 mail transfer requires development power and specialists. | 90 mail transfer requires development power and specialists. |