Just changed a "can" to a "could" since I don't know if most POP3 servers are

[mmh] / man / msgchk.man

diff --git a/man/msgchk.man b/man/msgchk.man
index e7624a0..2f1fed5 100644 (file)
--- a/man/msgchk.man
+++ b/man/msgchk.man
@@ -20,6 +20,9 @@ msgchk
 %nmhbeginpop%
 \%[\-host\ hostname]
 \%[\-user\ username]
+\%[\-kpop]
+\%[\-sasl]
+\%[\-saslmech \mechanism]
 .br
 %nmhendpop%
 \%[users\ ...]
@@ -75,6 +78,22 @@ you.
 For debugging purposes, there is also a switch `\-snoop', which will
 allow you to watch the POP transaction take place between you and the
 POP server.
+
+If nmh has been compiled with KPOP #defined, the `\-kpop' switch will allow
+\fImsgchk\fR to use Kerberized POP rather than standard POP3 on a given
+invocation.  If POPSERVICE was also #defined to "kpop", \fImsgchk\fR will be
+hardwired to always use KPOP.
+
+If nmh has been compiled with SASL support, the `\-sasl' switch will enable
+the use of SASL authentication.  Depending on the SASL mechanism used, this
+may require an additional password prompt from the user (but the
+\*(lq.netrc\*(rq file can be used to store this password).  The
+`\-saslmech' switch can be used to select a particular SASL mechanism.
+
+If SASL authentication is successful, \fIinc\fR will attempt to negotiate
+a security layer for session encryption.  Encrypted traffic is labelled
+with `(encrypted)' and `(decrypted)' when viewing the POP transaction
+with the `\-snoop' switch.
 %nmhendpop%
 .Fi
 ^$HOME/\&.mh\(ruprofile~^The user profile