.\"
.\" %nmhwarning%
.\"
-.TH SEND %manext1% "August 14, 2016" "%nmhversion%"
+.TH SEND %manext1% "October 10, 2016" "%nmhversion%"
.SH NAME
send \- send a message
.SH SYNOPSIS
.IR port-name/number ]
.RB [ \-sasl ]
.RB [ \-nosasl ]
-.RB [ \-saslmaxssf
-.IR ssf ]
.RB [ \-saslmech
.IR mechanism ]
.RB [ \-authservice
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
man page description of
.B \-snoop
for its other features.
-The
-.B \-saslmaxssf
-switch can be used to select the maximum value of the Security Strength Factor.
-This is an integer value and the exact meaning of this value depends on the
-underlying SASL mechanism. A value of 0 disables encryption.
.PP
If
.B nmh
has been compiled with OAuth support, the
+.B \-sasl
+and
.B \-saslmech xoauth2
-switch will enable OAuth authentication. The
+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
-.B mhlogin
+.IR mhlogin (1)
man page for more details.
.PP
If
.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