X-Git-Url: http://git.marmaro.de/?p=mmh;a=blobdiff_plain;f=man%2Fmsgchk.man;h=4c8a53abcbf5a13605e017ea28566d7812485f5d;hp=5054c339c9eca95d72631f17f1a7ad8b659d680b;hb=2c1aaf8b1495d2c7368b47edb04e9a2b7628377b;hpb=b1be76de8f184485753349ec27b2cdf2a4530965

diff --git a/man/msgchk.man b/man/msgchk.man
index 5054c33..4c8a53a 100644
--- a/man/msgchk.man
+++ b/man/msgchk.man
@@ -5,7 +5,7 @@
 .\" include the -mh macro file
 .so %etcdir%/tmac.h
 .\"
-.TH MSGCHK %manext1% MH.6.8 [%nmhversion%]
+.TH MSGCHK %manext1% "%nmhdate%" MH.6.8 [%nmhversion%]
 .SH NAME
 msgchk \- check for messages
 .SH SYNOPSIS
@@ -20,7 +20,12 @@ msgchk
 %nmhbeginpop%
 \%[\-host\ hostname]
 \%[\-user\ username]
+\%[\-apop]
+\%[\-noapop]
 \%[\-kpop]
+\%[\-sasl]
+\%[\-saslmech \mechanism]
+\%[\-snoop]
 .br
 %nmhendpop%
 \%[users\ ...]
@@ -77,10 +82,32 @@ 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 APOP #defined, the `\-apop' switch will cause
+\fImsgchk\fR to use APOP rather than standard POP3 authentication.  Under APOP,
+a unique string (generally of the format
+<\fIpid\fR.\fItimestamp\fR@\fIhostname\fR>) is announced by the POP server.
+Rather than `USER \fIuser\fR', `PASS \fIpassword\fR', msgchk sends `APOP
+\fIuser\fR \fIdigest\fR', where digest is the MD5 hash of the unique string
+followed by a `secret' shared by client and server, essentially equivalent to
+the user's password (though an APOP-enabled POP3 server could have separate APOP
+and plain POP3 passwords for a single user).  `\-noapop' disables APOP in cases
+where it'd otherwise be used.
+
 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