-.TH SEND %manext1% 2016-11-02 "%nmhversion%"
+.TH SEND %manext1% 2017-05-11 "%nmhversion%"
.
.\" %nmhwarning%
.
will scan the message draft for a header named
.IR Attach .
The draft is converted to a MIME message if one or more matches are found.
-This conversion occurs before all other processing. The
+This conversion occurs before all other processing.
.IR whatnow (1)
-man page describes the user interface for managing MIME attachments via
+describes the user interface for managing MIME attachments via
this mechanism.
.PP
The first part of the MIME message is the draft body if that body contains
the
.B nmh
draft folder facility. This is an advanced (and highly
-useful) feature. Consult the
+useful) feature. Consult
.IR mh-draft (5)
-man page for more
+for more
information.
.PP
If
.PP
If a message with multiple \*(lqFrom:\*(rq
addresses does
-.B NOT
+.I 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.
the appended fields and field reformatting. The \*(lqFcc:\*(rq fields
will be removed from all outgoing copies of the message.
.PP
+Beware that if an \*(lqFcc:\*(rq with one or more folders is present
+but none of the folders exist, and the default
+.I fileproc
+and
+.I postproc
+are in use, then
+.B refile
+will prompt the user to create the folder(s) if
+.B \-push
+is not specified. If all responses are negative, or creation of each folder
+fails, or
+.B \-push
+is specified, the message will not be copied to any folder and will be
+removed by
+.BR post .
+With the default
+.B refile
+switches, the message draft will be renamed according to the specification
+of its
+.B \-nolink
+switch.
+.PP
By using the
.B \-width
.I columns
.B \-port
switches can be used to override the default mail server (defined by the
.I %nmhetcdir%/mts.conf
-.RI servers
+.I servers
entry). The
.B \-snoop
switch can be used to view the SMTP transaction. (Beware that the
SASL mechanism used, this may require an additional password prompt from the
user (but the
.I netrc
-file can be used to store this password, as described in the
-mh-profile(5) man page). The
+file can be used to store this password, as described in
+.IR mh-profile (5).
+The
.B \-saslmech
switch can be used to select a particular SASL mechanism,
and the
.B \-user
switch can be used to select a authorization userid to provide to SASL
-other than the default. The credentials profile entry in the
-mh\-profile(5) man page describes the ways to supply a username and
+other than the default. The credentials profile entry in
+.IR mh\-profile (5)
+describes the ways to supply a username and
password.
.PP
If SASL authentication is successful,
-.BR nmh
+nmh
will attempt to negotiate a security layer for session encryption.
Encrypted data is labelled with `(encrypted)' and `(decrypted)' when
viewing the SMTP transaction with the
.B \-snoop
-switch; see the
-.B post
-man page description of
+switch; see
+.IR post (8)'s
+description of
.B \-snoop
for its other features.
.PP
switch. Before using OAuth authentication, the user must authorize nmh by
running
.B mhlogin
-and grant authorization to that account. See the
+and grant authorization to that account. See
.IR mhlogin (1)
-man page for more details.
+for more details.
.PP
If
.B nmh
is labelled with `(tls-encrypted)' and
`(tls-decrypted)' when viewing the SMTP transaction with the
.B \-snoop
-switch; see the
-.B post
-man page description of
+switch; see
+.IR post (8)'s
+description of
.B \-snoop
for its other features.
The
.RE
.fi
.PP
-For more information on authentication to mail servers, see the
+For more information on authentication to mail servers, see
.IR mhlogin (1)
-man page for OAuth services, and
+for OAuth services, and
.IR mh-profile (5)
-man page for login credentials.
+for login credentials.
.PP
.SH FILES
.fc ^ ~
.IR mhbuild (1),
.IR mhparam (1),
.IR mhlogin (1),
+.IR refile (1),
.IR repl (1),
.IR whatnow (1),
.IR mh\-alias (5),