Corrected date in forw man page.

[nmh] / man / send.man

diff --git a/man/send.man b/man/send.man
index 5a2f31391631114b549bcf52f2be7ab164df777d..2bce76a2e215efae72cfcdccadf3c69ce524a1e9 100644 (file)
--- a/man/send.man
+++ b/man/send.man
@@ -1,7 +1,7 @@
 .\"
 .\" %nmhwarning%
 .\"
-.TH SEND %manext1% "August 14, 2016" "%nmhversion%"
+.TH SEND %manext1% "October 10, 2016" "%nmhversion%"
 .SH NAME
 send \- send a message
 .SH SYNOPSIS
@@ -389,7 +389,7 @@ entry).  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
@@ -435,12 +435,13 @@ and
 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)
@@ -519,7 +520,7 @@ Here is an example profile entry using OAuth for an account hosted by gmail:
 .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