X-Git-Url: http://git.marmaro.de/?p=mmh;a=blobdiff_plain;f=man%2Fmh-tailor.man5;h=591871439377321232189df502386c7516e45d3c;hp=265c3cfddf489b09f55056397efca29b68f60ef3;hb=b14ea6073f77b4359aaf3fddd0e105989db9f306;hpb=684ec30d81e1223a282764452f4902ed4ad1c754

diff --git a/man/mh-tailor.man5 b/man/mh-tailor.man5
index 265c3cf..5918714 100644
--- a/man/mh-tailor.man5
+++ b/man/mh-tailor.man5
@@ -33,37 +33,10 @@ local copy of
 .PP
 .BR masquerade:
 .RS 5
-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 \*(lqdraft_from\*(rq, \*(lqmmailid\*(rq, and
-\*(lqusername_extension\*(rq.
+This directive controls email address masquerading.
+The possible value is \*(lqusername_extension\*(rq.
 .PP
-\*(lqmmailid\*(rq was the only type of masquerading in the original MH package, and
-apparently stands for \*(lqmasquerade mail identification\*(rq.  This type of
-masquerading keys off of the GECOS field of the passwd file.  When enabled,
-.B nmh
-will check if the user's pw_gecos field in the passwd file is of the
-form:
-.PP
-.RS 5
-Full Name <fakeusername>
-.RE
-.PP
-If it is, the internal
-.B nmh
-routines that find the username and full name
-of that user will return \*(lqfakeusername\*(rq and \*(lqFull Name\*(rq 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 \*(lqFirst.Last\*(rq sendmail aliases for all users.  If this is
-the case, the GECOS field for each user should look like:
-.PP
-.RS 5
-First [Middle] Last <First.Last>
-.RE
-.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
@@ -88,20 +61,12 @@ generating \*(lq[Resent\-]From:\*(rq lines and the SMTP envelope
 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 :
@@ -113,21 +78,6 @@ file.
 See
 .BR slocal (1)
 for the details.
-.RE
-.PP
-.BR everyone :
-200
-.RS 5
-The highest user-id which should NOT receive mail addressed to
-\*(lqeveryone\*(rq.
-.RE
-.PP
-.BR noshell :
-.RS 5
-If set, then each user-id greater than \*(lqeveryone\*(rq that has a
-login shell equivalent to the given value (e.g., \*(lq/bin/csh\*(rq)
-indicates that mail for \*(lqeveryone\*(rq should not be sent to them.
-This is useful for handling admin, dummy, and guest logins.
 .SS "File Locking"
 A few words on locking:
 .B nmh