-.TH INC %manext1% "August 14, 2016" "%nmhversion%"
+.TH INC %manext1% "October 9, 2016" "%nmhversion%"
.\"
.\" %nmhwarning%
.\"
.BR \-snoop ,
which will allow you to watch the POP transaction take place
between you and the POP server. If
-.B \-saslmech xoauth2
+.B \-sasl \-saslmech xoauth2
is used, the HTTP transaction is also shown.
.PP
If
-.TH MSGCHK %manext1% "August 14, 2016" "%nmhversion%"
+.TH MSGCHK %manext1% "October 9, 2016" "%nmhversion%"
.\"
.\" %nmhwarning%
.\"
which will
allow you to watch the POP transaction take place between you and the
POP server. If
-.B \-saslmech xoauth2
+.B \-sasl \-saslmech xoauth2
is used, the HTTP transaction is also shown.
.PP
If
If
.B nmh
has been compiled with OAuth support, the
-.B \-saslmech xoauth2
+.B \-sasl \-saslmech xoauth2
switch will enable OAuth authentication. The
.B \-user
switch must be used, and the
.\"
.\" %nmhwarning%
.\"
-.TH SEND %manext1% "August 14, 2016" "%nmhversion%"
+.TH SEND %manext1% "October 9, 2016" "%nmhversion%"
.SH NAME
send \- send a message
.SH SYNOPSIS
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
.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