Add ToLower(s) and ToUpper(s).

[nmh] / man / send.man

diff --git a/man/send.man b/man/send.man
index 5a2f31391631114b549bcf52f2be7ab164df777d..757eaced23d3856cb184b3c05d6246d9e2c624ab 100644 (file)
--- a/man/send.man
+++ b/man/send.man
@@ -1,13 +1,15 @@
 .\"
 .\" %nmhwarning%
 .\"
 .\"
 .\" %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
 .SH NAME
 send \- send a message
 .SH SYNOPSIS
 .HP 5
 .na
 .B send

+.RB [ \-help ]
+.RB [ \-version ]

 .RB [ \-alias
 .IR aliasfile ]
 .RB [ \-draft ]
 .RB [ \-alias
 .IR aliasfile ]
 .RB [ \-draft ]


@@ -54,8 +56,6 @@ send \- send a message
 .IR columns ]
 .RB [ file
 \&...]
 .IR columns ]
 .RB [ file
 \&...]

-.RB [ \-version ]
-.RB [ \-help ]

 .ad
 .SH DESCRIPTION
 .B Send
 .ad
 .SH DESCRIPTION
 .B Send


@@ -263,7 +263,7 @@ If a \*(lqDcc:\*(rq field is encountered and the
 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
 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
 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


@@ -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
 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
 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
 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
 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)
 .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
 .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
 .RS 5
 -authservice gmail -tls -server smtp.gmail.com
 -user gmail_login@example.com