X-Git-Url: http://git.marmaro.de/?p=mmh;a=blobdiff_plain;f=man%2Fpost.man;h=ca406044c2a84744e1bb7a8e41526ead469224e1;hp=69374ce985ffba44b6a363916c56b8151d871061;hb=2c1aaf8b1495d2c7368b47edb04e9a2b7628377b;hpb=cfc525a9b85207225cb4071d1d3b01e8d1db2424

diff --git a/man/post.man b/man/post.man
index 69374ce..ca40604 100644
--- a/man/post.man
+++ b/man/post.man
@@ -5,7 +5,7 @@
 .\" include the -mh macro file
 .so %etcdir%/tmac.h
 .\"
-.TH POST %manext8% MH.6.8 [%nmhversion%]
+.TH POST %manext8% "%nmhdate%" MH.6.8 [%nmhversion%]
 .SH NAME
 post \- deliver a message
 .SH SYNOPSIS
@@ -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