Just changed a "can" to a "could" since I don't know if most POP3 servers are

[mmh] / man / mh-tailor.man

diff --git a/man/mh-tailor.man b/man/mh-tailor.man
index 53c0875..b9f2560 100644 (file)
--- a/man/mh-tailor.man
+++ b/man/mh-tailor.man
@@ -27,6 +27,21 @@ default values and a description of their meanings are listed below:
 
 .in +.5i
 .ti -.5i
 
 .in +.5i
 .ti -.5i

+mts:
+.br
+The mail transport method to use.  The two acceptable options are \fBsmtp\fP
+(which is the default), and \fBsendmail\fP.
+
+If you use \fBsmtp\fP, this will enable a direct SMTP (simple mail transport
+protocol) interface in \fInmh\fR.  When sending mail, instead of passing the
+message to the mail transport agent, \fIpost\fR will open a socket connection
+to the mail port on the machine specified in the \fIservers\fR entry.
+
+If you use \fBsendmail\fP, then \fIpost\fR will send messages by forking a
+local copy of sendmail.  Currently it will still speak SMTP with this local
+copy of sendmail.
+
+.ti -.5i

 localname:
 .br
 The hostname \fInmh\fR considers local.  It should typically be a fully
 localname:
 .br
 The hostname \fInmh\fR considers local.  It should typically be a fully

@@ -136,7 +151,11 @@ versions of sendmail for which "plussed user" processing is active can set
 \fB$USERNAME_EXTENSION\fR to "+\fIstring\fR".  These MTA features are useful
 because they allow one to use different email addresses in different situations
 (to aid in automatic mail filtering or in determining where spammers got one's
 \fB$USERNAME_EXTENSION\fR to "+\fIstring\fR".  These MTA features are useful
 because they allow one to use different email addresses in different situations
 (to aid in automatic mail filtering or in determining where spammers got one's

-address) while only actually having a single account.
+address) while only actually having a single account.  Note that
+\fB$USERNAME_EXTENSION\fR is only appended to the username when \fIpost\fR is
+generating "[Resent\-]From:" lines and the SMTP envelope "From:".  \fIinc\fR,
+for instance, will not try to read from a maildrop file called "dan\-www" (to
+recall the earlier example).

 
 "draft_from" controls the most powerful type of address masquerading.  Normally,
 when a user explicitly specifies a "From:" header in a draft, \fInmh\fR uses it
 
 "draft_from" controls the most powerful type of address masquerading.  Normally,
 when a user explicitly specifies a "From:" header in a draft, \fInmh\fR uses it

@@ -172,8 +191,7 @@ This is useful for handling admin, dummy, and guest logins.
 
 .in -.5i
 .Uh "SMTP support"
 
 .in -.5i
 .Uh "SMTP support"

-These options are only available if you compiled \fInmh\fP with the
-\*(lq/smtp\*(rq support.
+These options are only available if you set \fImts\fR to \fBsmtp\fP.

 
 .in +.5i
 .ti -.5i
 
 .in +.5i
 .ti -.5i

@@ -208,8 +226,7 @@ ignored (sorry, the interface went away under BIND).
 
 .in -.5i
 .Uh "SendMail"
 
 .in -.5i
 .Uh "SendMail"

-This option is only available if you compiled \fInmh\fP to use
-\fISendMail\fP as your delivery agent.
+This option is only available if you set \fImts\fR to \fBsendmail\fP.

 
 .in +.5i
 .ti -.5i
 
 .in +.5i
 .ti -.5i

@@ -220,7 +237,7 @@ The pathname to the \fIsendmail\fR program.
 .in -.5i
 .Uh "Post Office Protocol"
 This option is only available if you have compiled \fInmh\fP with POP
 .in -.5i
 .Uh "Post Office Protocol"
 This option is only available if you have compiled \fInmh\fP with POP

-support enabled (i.e., \*(lq--enable-nmh-pop\*(rq).
+support enabled (i.e., \*(lq--enable-pop\*(rq).

 
 .in +.5i
 .ti -.5i
 
 .in +.5i
 .ti -.5i