X-Git-Url: http://git.marmaro.de/?p=mmh;a=blobdiff_plain;f=man%2Fpost.man;h=23841f788da969e71586f3c8b0f9d28a2e619ca4;hp=45261778f4d7250c95e3a6c4e1eb522063ca1de7;hb=9892129b33a8da3329f6331078a94a18ff8fe0e2;hpb=077b355833f623241d5d145810b91da60e4c260c

diff --git a/man/post.man b/man/post.man
index 4526177..23841f7 100644
--- a/man/post.man
+++ b/man/post.man
@@ -24,6 +24,7 @@ post \- deliver a message
 \%[\-noverbose]
 \%[\-watch] \%[\-nowatch]
 \%[\-width\ columns]
+\%[\-sasl] \%[\-saslmech\ mechanism] \%[\-user\ username]
 .br
 file
 \%[\-version]
@@ -116,6 +117,20 @@ account, or when remote email robots give improper precedence to the envelope
 "From:".  Note that your MTA may still reveal your real identity (e.g.
 sendmail's "X\-Authentication\-Warning:" header). 
 
+If nmh has been compiled with SASL support, the `\-sasl' switch will enable
+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 \*(lq.netrc\*(rq file can be used to store this password).
+`\-saslmech' switch can be used to select a particular SASL mechanism,
+and the the `\-user' switch can be used to select a authorization userid
+to provide to SASL other than the default.
+
+Currently SASL security layers are not supported for SMTP.  nmh's SMTP SASL code
+will always negotiate an unencrypted connection.  This means that while the SMTP
+authentication can be encrypted, the subsequent data stream can not.  This is in
+contrast to nmh's POP3 SASL support, where encryption is supported for both the
+authentication and the data stream.
+
 .Fi
 ^%etcdir%/mts.conf~^nmh mts configuration file
 ^%etcdir%/MailAliases~^global nmh alias file