Generalized condition for support of parameter value tests.

[nmh] / man / mh-mail.man

diff --git a/man/mh-mail.man b/man/mh-mail.man
index b2a430cb4d8efa2c06e1cc0d5aeec7077a3f773d..4a5e8b581ab45fabd8a1ad072491abf2c8631dc2 100644 (file)
--- a/man/mh-mail.man
+++ b/man/mh-mail.man
@@ -1,4 +1,4 @@
-.TH MH-MAIL %manext5% "July 9, 2012" "%nmhversion%"
+.TH MH-MAIL %manext5% "January 8, 2014" "%nmhversion%"
 .\"
 .\" %nmhwarning%
 .\"
@@ -17,7 +17,7 @@ can read message files in that antiquated format.
 Each user possesses a mail drop box which initially receives all messages
 processed by
 .BR post .
-.B Inc
+.B inc
 will read from that drop
 box and incorporate the new messages found there into the user's own
 mail folders (typically
@@ -28,14 +28,14 @@ Messages are expected to consist of lines of text.  Graphics and binary
 data are not handled.  No data compression is accepted.  All text is
 clear ASCII 7-bit data.
 .PP
-The general \*(lqmemo\*(rq framework of RFC\-822 is used.  A message
+The general \*(lqmemo\*(rq framework of RFC 822 is used.  A message
 consists of a block of information in a rigid format, followed by
 general text with no specified format.  The rigidly formatted first
 part of a message is called the header, and the free-format portion is
 called the body.  The header must always exist, but the body is optional.
 These parts are separated by an empty line, i.e., two consecutive newline
 characters.  Within
-.B nmh ,
+.BR nmh ,
 the header and body may be separated by a line consisting of dashes:
 .PP
 .RS 5
@@ -56,7 +56,7 @@ are indicated by leading spaces or tabs.
 Each header item is called a component and is composed of a keyword or
 name, along with associated text.  The keyword begins at the left margin,
 may NOT contain spaces or tabs, may not exceed 63 characters (as specified
-by RFC\-822), and is terminated by a colon (`:').  Certain components
+by RFC 822), and is terminated by a colon (`:').  Certain components
 (as identified by their keywords) must follow rigidly defined formats
 in their text portions.
 .PP
@@ -105,6 +105,19 @@ header MUST exist when the message is sent to
 otherwise the message will be rejected.
 .RE
 .PP
+.BR Envelope\-From :
+.RS 5
+Used by
+.B post
+to specify a value for the sender's envelope address to the mail transport
+system.  If omitted, 
+.B post
+will use the value of the \*(lqSender:\*(rq or the \*(lqFrom:\*(rq header.
+See
+.IR send (1)
+for more details.
+.RE
+.PP
 .BR Mail\-Reply\-To :
 .RS 5
 For a standard reply (using
@@ -172,7 +185,7 @@ uses an encapsulation method for blind copies, see
 .RS 5
 Still more recipients.  However, the \*(lqDcc:\*(rq line is not
 copied onto the messages as delivered.  Recipients on the \*(lqDcc:\*(rq
-line receive the same messsage as recipients on the \*(lqTo:\*(rq and
+line receive the same message as recipients on the \*(lqTo:\*(rq and
 \*(lqcc:\*(rq lines.  See
 .IR send (1)
 for more details.
@@ -220,8 +233,10 @@ Added when redistributing a message by
 .PP
 .BR Resent\-From :
 .RS 5
-Added when redistributing a message by
-.BR post .
+Used instead of the \*(lqFrom:\*(rq header when
+.B post 
+redistributes a message.  See \*(lqFrom:\*(rq for more information about
+this header is used.
 .RE
 .PP
 .BR Resent\-To:
@@ -232,12 +247,12 @@ New recipients for a message resent by
 .PP
 .BR Resent\-cc :
 .RS 5
-Still more recipients. See \*(lqcc:\*(rq and \*(lqResent\-To:\*(rq.
+Still more recipients.  See \*(lqcc:\*(rq and \*(lqResent\-To:\*(rq.
 .RE
 .PP
 .BR Resent\-Bcc :
 .RS 5
-Even more recipients. See \*(lqBcc:\*(rq and \*(lqResent\-To:\*(rq.
+Even more recipients.  See \*(lqBcc:\*(rq and \*(lqResent\-To:\*(rq.
 .RE
 .PP
 .BR Resent\-Fcc :
@@ -282,15 +297,22 @@ under the
 .B \-annotate
 option.
 .RE
+.PP
+.BR Attach :
+.RS 5
+Used by
+.B mhbuild
+to specify a filename to attach to this message.  See
+.IR mhbuild (1)
+for more information.
+.RE
 .SH FILES
-.fc ^ ~
-.nf
-.ta \w'%etcdir%/ExtraBigFileName  'u
-^%mailspool%/$USER~^Location of mail drop
-.fi
+.TP 20
+%mailspool%/$USER
+Location of mail drop.
 .SH "SEE ALSO"
 .I
 Standard for the Format of ARPA Internet Text Messages
-(RFC\-822)
+(RFC 822)
 .SH CONTEXT
 None