Added note that suffixes were removed from filenames of temporary files.

[nmh] / man / post.man

diff --git a/man/post.man b/man/post.man
index bd048c0df717fa550e96bbe469eaca61c2c2bfcd..4d64300cc75ae57148faa3ecf48f1ec1ffb26558 100644 (file)
--- a/man/post.man
+++ b/man/post.man
@@ -1,7 +1,7 @@
+.TH POST %manext8% "April 14, 2013" "%nmhversion%"
 .\"
 .\" %nmhwarning%
 .\"
-.TH POST %manext8% "%nmhdate%" MH.6.8 [%nmhversion%]
 .SH NAME
 post \- deliver a message
 .SH SYNOPSIS
@@ -37,6 +37,7 @@ post \- deliver a message
 .RB [ \-user
 .IR username ]
 .RB [ \-tls ]
+.RB [ \-initialtls ]
 .RB [ \-notls ]
 .I file
 .RB [ \-version ]
@@ -144,7 +145,7 @@ delivery).
 Under normal circumstances,
 .B post
 uses the \*(lqFrom:\*(rq line in the message draft as the identity of
-the the originating mailbox.  A \*(lqFrom:\*(rq line is required in
+the originating mailbox.  A \*(lqFrom:\*(rq line is required in
 all message draft.  By default the message composition utilities such
 as
 .BR comp ,
@@ -203,14 +204,17 @@ switches will enable and disable
 the use of SASL authentication with the SMTP MTA.  Depending on the
 SASL mechanism used, this may require an additional password prompt from the
 user (but the
-.RI \*(lq \&.netrc \*(rq
-file can be used to store this password).
+.I netrc
+file can be used to store this password, as described in the
+mh-profile(5) man page).  The
 .B \-saslmech
 switch can be used to select a particular SASL mechanism,
-and the the
+and the
 .B \-user
-switch can be used to select a authorization userid
-to provide to SASL other than the default.
+switch can be used to select a authorization userid to provide to SASL
+other than the default.  The credentials profile entry in the
+mh_profile(5) man page describes the ways to supply a username and
+password.
 .PP
 If SASL authentication is successful, 
 .BR nmh
@@ -229,14 +233,22 @@ If
 has been compiled with TLS support, the
 .B \-tls
 and
-.B \-notls
-switches will require and disable the negotiation of TLS support when
-connecting to the
-SMTP MTA.  Encrypted data is labelled with `(tls-encrypted)' and
+.B \-initialtls
+switches will require the negotiation of TLS when
+connecting to the SMTP MTA.  The
+.B \-tls
+switch will negotiate TLS as part of the normal SMTP protocol
+using the STARTTLS command.  The
+.B \-initialtls
+will negotiate TLS immediately after the connection has
+taken place, before any SMTP commands are sent or received.  Encrypted data
+is labelled with `(tls-encrypted)' and
 `(tls-decrypted)' when viewing the SMTP transction with the
 .B \-snoop
 switch.
-
+The
+.B \-notls
+switch will disable all attempts to negotiate TLS.
 .SH FILES
 .fc ^ ~
 .nf
@@ -246,19 +258,22 @@ switch.
 ^%bindir%/refile~^Program to process Fcc:s
 ^%libdir%/mhl~^Program to process Bcc:s
 .fi
-
 .SH "PROFILE COMPONENTS"
 .B post
 does
 .B NOT
 consult the user's
 .I \&.mh\(ruprofile
-
 .SH "SEE ALSO"
-mhmail(1), send(1), mh\-mail(5), mh\-alias(5), mh\-tailor(5),
+.IR mhmail (1),
+.IR send (1),
+.IR mh\-mail (5),
+.IR mh\-alias (5),
+.IR mh\-profile (5),
+.IR mh\-tailor (5)
+.PP
 .I "Standard for the Format of ARPA Internet Text Messages"
-(RFC\-822)
-
+(RFC 822)
 .SH DEFAULTS
 .nf
 .RB ` \-alias "' defaults to %etcdir%/MailAliases"
@@ -271,12 +286,10 @@ mhmail(1), send(1), mh\-mail(5), mh\-alias(5), mh\-tailor(5),
 .RB ` "\-width\ 72" '
 .RB ` \-nofilter '
 .fi
-
 .SH CONTEXT
 None
-
 .SH BUGS
 \*(lqReply\-To:\*(rq fields are allowed to have groups in them according
-to the 822 specification, but
+to the RFC 822 specification, but
 .B post
 won't let you use them.