X-Git-Url: http://git.marmaro.de/?a=blobdiff_plain;f=man%2Fsend.man;h=9bb28972224d382f1badc4cdc23c9b862ff08b10;hb=22a08fd1babf7a0a5602684ea0c6c2485e15f6d9;hp=43d1ad1278f3a50dd6ea04d072f50be22781017b;hpb=1691e80890e5d8ba258c51c214a3e91880e1db2b;p=mmh

diff --git a/man/send.man b/man/send.man
index 43d1ad1..9bb2897 100644
--- a/man/send.man
+++ b/man/send.man
@@ -31,6 +31,7 @@ send
 .br
 \%[\-verbose] \%[\-noverbose]
 \%[\-watch] \%[\-nowatch]
+\%[\-sasl] \%[\-saslmech\ mechanism] \%[\-user\ username]
 .br
 \%[\-width\ columns]
 \%[file\ ...] 
@@ -132,6 +133,20 @@ will be removed from all outgoing copies of the message.
 By using the `\-width\ columns' switch, the user can direct \fIsend\fR
 as to how long it should make header lines containing addresses.
 
+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.
+
 The files specified by the profile entry \*(lqAliasfile:\*(rq and any
 additional alias files given by the `\-alias aliasfile' switch will be
 read (more than one file, each preceded by `\-alias', can be named).