1.1 --- a/ch03.roff	Thu Jun 21 00:01:13 2012 +0200
     1.2 +++ b/ch03.roff	Thu Jun 21 08:58:56 2012 +0200
     1.3 @@ -61,15 +61,28 @@
     1.4  Removing the mail transfer facilities had been the first work task
     1.5  in the mmh project.
     1.6  .P
     1.7 -The Mail Submission Agent (MSA) is called
     1.8 -\fIMessage Transfer Service\fP (MTS) in nmh.
     1.9 -The facility established network connections and spoke SMTP to submit
    1.10 +Focusing on one mail agent role only is motivated by Eric Allman's
    1.11 +experience with Sendmail.
    1.12 +He identified limiting Sendmail the MTA task had be one reason for
    1.13 +its success:
    1.14 +.[ [
    1.15 +costales sendmail
    1.16 +.], p. xviii]
    1.17 +.QS
    1.18 +Second, I limited myself to the routing function \(en
    1.19 +I wouldn't write user agents or delivery backends.
    1.20 +This was a departure of the dominant through of the time,
    1.21 +in which routing logic, local delivery, and often the network code
    1.22 +were incorporated directly into the user agents.
    1.23 +.QE
    1.24 +.P
    1.25 +In mmh, the Mail Submission Agent (MSA) is called
    1.26 +\fIMessage Transfer Service\fP (MTS).
    1.27 +This facility, implemented by the
    1.28 +.Pn post
    1.29 +command, established network connections and spoke SMTP to submit
    1.30  messages for relay to the outside world.
    1.31 -This part was implemented by the
    1.32 -.Pn post
    1.33 -command.
    1.34 -The changes in email in the last years
    1.35 -demanded changes in this part of nmh too.
    1.36 +The changes in email demanded changes in this part of nmh too.
    1.37  Encryption and authentication for network connections
    1.38  needed to be supported, hence TLS and SASL were introduced into nmh.
    1.39  This added complexity to nmh without improving it in its core functions.