Updated mhparam, man pages, and test-mhparam to reflect split

[nmh] / man / post.man

diff --git a/man/post.man b/man/post.man
index 4a5bb29508fc62f7422661b895ac5595a3785bdd..4d64300cc75ae57148faa3ecf48f1ec1ffb26558 100644 (file)
--- a/man/post.man
+++ b/man/post.man
@@ -1,4 +1,4 @@
-.TH POST %manext8% "March 31, 2013" "%nmhversion%"
+.TH POST %manext8% "April 14, 2013" "%nmhversion%"
 .\"
 .\" %nmhwarning%
 .\"
@@ -145,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 ,
@@ -204,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
@@ -266,10 +269,11 @@ consult the user's
 .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"
@@ -286,6 +290,6 @@ consult the user's
 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.