.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
The end-of-message delimiter for maildrops.
.ti -.5i
-mmailid: 0
+masquerade:
.br
-If this is non-zero, then activate support for MMailids (username
-masquerading). When this is activated, \fInmh\fR will check if the
-pw_gecos field in the password file has the form
+This directive controls three different types of email address masquerading.
+The three possible values, which may be specified in any combination on the
+line, separated by spaces, are "draft_from", "mmailid", and
+"username_extension".
+
+"mmailid" was the only type of masquerading in the original MH package, and
+apparently stands for "masquerade mail identification". This type of
+masquerading keys off of the GECOS field of the passwd file. When enabled,
+\fInmh\fR will check if the user's pw_gecos field in the passwd file is of the
+form:
.ti +.5i
Full Name <fakeusername>
-If the pw_gecos field has this form, then the internal \fInmh\fR
-routines that find the username and full name of a user will return
-\*(lqfakeusername\*(rq and \*(lqFull Name\*(rq respectively. If
-the pw_gecos field for a user is not of this form, there will be
-no username masquerading for that user.
+If it is, the internal \fInmh\fR routines that find the username and full name
+of that user will return "fakeusername" and "Full Name" respectively. This is
+useful if you want the messages you send to always appear to come from the name
+of an MTA alias rather than your actual account name. For instance, many
+organizations set up "First.Last" sendmail aliases for all users. If this is
+the case, the GECOS field for each user should look like:
-This facility is useful if you are using POP, and wish for messages
-that are sent by users to appear to originate from the username of
-their POP account, rather than their username on the local machine.
+.ti +.5i
+First [Middle] Last <First.Last>
+
+"username_extension", when specified on the "masquerade:" line, allows a second
+type of username masquerading. If the user sets the \fB$USERNAME_EXTENSION\fR
+environment variable, its value will be appended to the actual login name. For
+instance, if I am dan@company.com, and I set \fB$USERNAME_EXTENSION\fR to
+"\-www", my mail will appear to come from "dan\-www@company.com". This is meant
+to interact with qmail's "user\-extension" feature, where mail sent to
+\fIuser\fR\-\fIstring\fR will be delivered to \fIuser\fR. Likewise, those using
+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
+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
+rather than constructing its own. However, to discourage email forgery, the
+SMTP envelope "From:" and a "Sender:" header are set to the user's real address.
+When "draft_from" is turned on, though, the envelope "From:" will use the
+address specified in the draft, and there will be no "Sender:" header. This is
+useful when a user wants to pretend to be sending mail "directly" from a remote
+POP3 account, or when remote mail robots incorrectly use the envelope "From:" in
+preference to the body "From:" (or refuse to take action when the two don't
+match). Note that the MTA may still reveal the user's real identity (e.g.
+sendmail's "X\-Authentication\-Warning:" header).
.ti -.5i
maildelivery: %libdir%/maildelivery
.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
.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
.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
.Pr
None
.Sa
-mh\-mts(8)
+mh\-mts(8), post(8)
.De
As listed above
.Co
projects / mmh / blobdiff