.RB [ \-help ]
.RB [ \-attach
.IR header-field-name ]
+.RB [ \-noattach ]
.RB [ \-attachformat
.IR 0 " | " 1 " | " 2 ]
.ad
.BR post .
.PP
-If a
-.I header-field-name
-is supplied using the
-.B -attach
-option, the draft is scanned for a header whose field name matches the
-supplied
-.IR header-field-name .
+By default the draft is scanned for a header named
+.IR Nmh-Attachment .
The draft is converted to a MIME message if one or more matches are found.
-This conversion occurs before all other processing.
+This conversion occurs before all other processing. The header name
+can be changed with the
+.B \-attach
+option. This behavior can be disabled completely with the
+.B \-noattach
+option.
.PP
The first part of the MIME message is the draft body if that body contains
any non-blank characters.
is interpreted as a file name, and each file named is included as a separate
part in the MIME message.
.PP
-For file names with dot suffixes, the context is scanned for a
+For file names with dot suffixes, the profile is scanned for a
.I mhshow-suffix-
entry for that suffix.
-The content-type for the part is taken from that context entry if a match is
-found.
+The content-type for the part is taken from that profile entry if a match is
+found. If a match is not found in the user profile, the mhn.defaults
+profile is scanned next.
If no match is found or the file does not have a dot suffix, the content-type
is text/plain if the file contains only ASCII characters or application/octet-stream
-if it contains characters outside of the ASCII range.
+if it contains characters outside of the ASCII range. See
+.BR mhshow (1)
+for more details and example syntax.
.PP
Each part contains a name attribute that is the last component of the path name.
A
The
.B -attachformat
option specifies the MIME header field formats: a value of
-.B 0,
-the default,
+.B 0
includes the
.I x-unix-mode
attribute as noted above. A value of
-.B 1
+.BR 1 ,
+the default,
suppresses that, puts the file name in the
\*(lqContent-Description\*(rq header, and
adds a \*(lqContent-Disposition\*(rq header. A value of
field is required in this case. Otherwise a \*(lqSender:\*(rq field
is optional.
.PP
-When using SMTP for mail submission, the envelope\-from used for SMTP
-transaction is derived from the \*(lqFrom:\*(rq field. If multiple
-addresses are in the \*(lqFrom:\*(rq field, the address in the
-\*(lqSender\*(rq field is used instead. This behavior can be overridden
-by using the \*(lqEnvelope\-From:\*(rq field. When \*(lqEnvelope\-From\*(rq
-appears in the message, its address will be used as the SMTP envelope\-from
-address and the field will be removed from the message.
+If a message with multiple \*(lqFrom:\*(rq
+addresses does
+.B NOT
+include a \*(lqSender:\*(rq field but does include an \*(lqEnvelope\-From:\*(rq
+field, the \*(lqEnvelope\-From:\*(rq field will be used to construct
+a \*(lqSender:\*(rq field.
+.PP
+When using SMTP for mail submission, the envelope\-from used for the SMTP
+transaction is derived from the \*(lqEnvelope\-From:\*(rq field.
+If no \*(lqEnvelope\-From:\*(rq field is present, the \*(lqSender:\*(rq
+field is used. If neither the \*(lqEnvelope\-From:\*(rq nor the
+\*(lqSender:\*(rq field is present, the \*(lqFrom:\*(rq field is used.
+When \*(lqEnvelope\-From:\*(rq appears in a message
+it will be removed from the final outgoing message.
.PP
By using the
.B \-format
.RB ` \-noverbose '
.RB ` \-nowatch '
.RB ` "\-width\ 72" '
-.RB ` "\-attachformat\ 0" '
+.RB ` "\-attach\ Nmh-Attachment" '
+.RB ` "\-attachformat\ 1" '
.fi
.SH CONTEXT