X-Git-Url: http://git.marmaro.de/?a=blobdiff_plain;f=man%2Fpost.man;h=b6e395e324961e692d253c597cd4bedd9f3c7c02;hb=5dd6771b28c257af405d7248639ed0e3bcdce38b;hp=f437f62185d58b21a872ac255e004bb1fa3ccfa0;hpb=1524cb8c0b86a854149d7859d6a2503d61dbaa36;p=mmh

diff --git a/man/post.man b/man/post.man
index f437f62..b6e395e 100644
--- a/man/post.man
+++ b/man/post.man
@@ -1,6 +1,5 @@
 .\"
 .\" %nmhwarning%
-.\" $Id$
 .\"
 .TH POST %manext8% "%nmhdate%" MH.6.8 [%nmhversion%]
 .SH NAME
@@ -181,6 +180,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 +207,23 @@ 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 `(sasl-encrypted)' and `(sasl-decrypted)' when
+viewing the SMTP transaction with the
+.B \-snoop
+switch.
+.PP
+If
+.B nmh
+has been compiled with TLS support, the
+.B \-tls
+switch will require the negotiation of TLS support when connecting to the
+SMTP MTA.  Encrypted data is labelled with `(tls-encrypted)' and
+`(tls-decrypted)' when viewing the SMTP transction with the
+.B \-snoop
+switch.
 
 .SH FILES
 .fc ^ ~