X-Git-Url: http://git.marmaro.de/?a=blobdiff_plain;f=man%2Fpost.man;h=892215a2b9efea03d2746e1594a40a1eb20b03e8;hb=86048c14a070e3382577dd22519319bce77c70b9;hp=24a74bc4503f4c812fd0a12a5633afc930c92de6;hpb=1b5a1bd2244d3e1c12b7c9e1f48e445de5ad2ea2;p=mmh

diff --git a/man/post.man b/man/post.man
index 24a74bc..892215a 100644
--- a/man/post.man
+++ b/man/post.man
@@ -181,6 +181,16 @@ account, or when remote email robots give improper precedence to the envelope
 .BR sendmail 's
 \*(lqX\-Authentication\-Warning:\*(rq header). 
 .PP
+If nmh is using the SMTP MTA, the
+.B \-server
+and the
+.B \-port
+switches can be used to override the default mail server (defined by the
+.RI servers
+entry in
+.I %etcdir%/mts.conf
+).
+.PP
 If
 .B nmh
 has been compiled with SASL support, the
@@ -198,15 +208,13 @@ and the the
 switch can be used to select a authorization userid
 to provide to SASL other than the default.
 .PP
-Currently SASL security layers are not supported for SMTP.
-.BR 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
-.BR nmh 's
-POP3 SASL support, where encryption is supported for both the
-authentication and the data stream.
+If SASL authentication is successful, 
+.BR nmh
+will attempt to negotiate a security layer for session encryption.
+Encrypted data is labelled with `(encrypted)' and `(decrypted)' when
+viewing the SMTP transaction with the
+.B \-snoop
+switch.
 
 .SH FILES
 .fc ^ ~
@@ -245,7 +253,7 @@ mhmail(1), send(1), mh\-mail(5), mh\-alias(5), mh\-tailor(5),
 .SH CONTEXT
 None
 
-.Bu
+.SH BUGS
 \*(lqReply\-To:\*(rq fields are allowed to have groups in them according
 to the 822 specification, but
 .B post