.\"
.\" %nmhwarning%
.\"
-.TH SEND %manext1% "August 14, 2016" "%nmhversion%"
+.TH SEND %manext1% "October 10, 2016" "%nmhversion%"
.SH NAME
send \- send a message
.SH SYNOPSIS
.HP 5
.na
.B send
+.RB [ \-help ]
+.RB [ \-version ]
.RB [ \-alias
.IR aliasfile ]
.RB [ \-draft ]
.IR columns ]
.RB [ file
\&...]
-.RB [ \-version ]
-.RB [ \-help ]
.ad
.SH DESCRIPTION
.B Send
mail transport method is not in use, its addresses will be used for
delivery, and the \*(lqDcc:\*(rq field will be removed from the message. The
blind recipients will receive the same message sent to the sighted
-recipients. *WARNING* Recipients listed in the \*(lqDcc:\*(rq field receive no
+recipients. *WARNING* Recipients listed in the \*(lqDcc:\*(rq field receive no
explicit indication that they have received a \*(lqblind copy\*(rq.
This can cause blind recipients to
inadvertently reply to all of the sighted recipients of the
switch can be used to view the SMTP transaction. (Beware that the
SMTP transaction may contain authentication information either in
plaintext or easily decoded base64.) If
-.B \-saslmech xoauth2
+.B \-sasl \-saslmech xoauth2
is used, the HTTP transaction is also shown.
.PP
If
switches will enable OAuth authentication. The
.B \-user
switch must be used, and the
-.I user-name
+.I username
must be an email address the user has for the service, which must
be specified with the
.B \-authservice
.I service
-switch. Before using this, the user must authorize nmh by running
+switch. Before using OAuth authentication, the user must authorize nmh by
+running
.B mhlogin
and grant authorization to that account. See the
.IR mhlogin (1)
.PP
.nf
.RS 5
-sendfrom-gmail_address@example.com: -saslmech xoauth2
+sendfrom-gmail_address@example.com: -sasl -saslmech xoauth2
.RS 5
-authservice gmail -tls -server smtp.gmail.com
-user gmail_login@example.com