+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
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
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