Clarified post.man and send.man for those not completely up on SASL terminology.

"SASL encryption layers are not supported for SMTP" means that encryption is
supported for the authentication but not for the subsequent data stream.

diff --git a/ChangeLog b/ChangeLog
index f84fb89..5958552 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,10 @@
+Tue Jul 11 14:18:01 2000 Dan Harkless <dan-nmh@dilvish.speed.net>
+
+       * Clarified post.man and send.man for those not completely up on
+       SASL terminology.  "SASL encryption layers are not supported for
+       SMTP" means that encryption is supported for the authentication
+       but not for the subsequent data stream.
+
 Sat Jul  8 01:36:19 EDT 2000 Ken Hornstein <kenh@cmf.nrl.navy.mil>
 
        * Added SASL support for IMAP, POP and SMTP.  SASL encryption

diff --git a/man/post.man b/man/post.man
index 69374ce..23841f7 100644 (file)
--- a/man/post.man
+++ b/man/post.man
@@ -125,8 +125,11 @@ user (but the \*(lq.netrc\*(rq file can be used to store this password).
 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.  The SASL
-SMTP code in nmh will always negotiate an unencrypted connection.
+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

diff --git a/man/send.man b/man/send.man
index 88fd9c3..9bb2897 100644 (file)
--- a/man/send.man
+++ b/man/send.man
@@ -141,8 +141,11 @@ user (but the \*(lq.netrc\*(rq file can be used to store this password).
 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.  The SASL
-SMTP code in nmh will always negotiate an unencrypted connection.
+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