.PP
.BR masquerade:
.RS 5
-This directive controls two different types of email address masquerading.
-The two possible values, which may be specified in any combination on the
-line, separated by spaces, are \*(lqdraft_from\*(rq and
-\*(lqusername_extension\*(rq.
+This directive controls email address masquerading.
+The possible value is \*(lqusername_extension\*(rq.
.PP
-\*(lqusername_extension\*(rq, when specified on the \*(lqmasquerade:\*(rq line, allows a second
-type of username masquerading. If the user sets the
+If specified and if the user sets the
.B $USERNAME_EXTENSION
environment variable, its value will be appended to the actual login name. For
instance, if I am \*(lqdan@company.com\*(rq, and I set
for instance, will not try to read from a maildrop file called \*(lqdan\-www\*(rq (to
recall the earlier example).
.PP
-\*(lqdraft_from\*(rq controls the most powerful type of address masquerading. Normally,
-when a user explicitly specifies a \*(lqFrom:\*(rq header in a draft,
+In any case:
+When a user explicitly specifies a \*(lqFrom:\*(rq header in a draft,
.B nmh
uses it
rather than constructing its own. However, to discourage email forgery, the
SMTP envelope \*(lqFrom:\*(rq and a \*(lqSender:\*(rq header are set to the user's real address.
-When \*(lqdraft_from\*(rq is turned on, though, the envelope \*(lqFrom:\*(rq will use the
-address specified in the draft, and there will be no \*(lqSender:\*(rq header. This is
-useful when a user wants to pretend to be sending mail \*(lqdirectly\*(rq from a remote
-POP3 account, or when remote mail robots incorrectly use the envelope \*(lqFrom:\*(rq in
-preference to the body \*(lqFrom:\*(rq (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.
-.BR sendmail 's
-\*(lqX\-Authentication\-Warning:\*(rq header).
.RE
.PP
.BR maildelivery :