+Tue Dec 19 19:16:37 2000 Dan Harkless <dan-nmh@dilvish.speed.net>
+
+ * -apop and -noapop were not documented in inc.man. -snoop was
+ documented but didn't appear in the usage SYNOPSIS.
+
Thu Dec 14 14:32:09 2000 Shantonu Sen <ssen@mit.edu>
* Updated config.guess and config.sub to the most recent
\%[\-user\ username]
\%[\-pack\ file]
\%[\-nopack]
+\%[\-apop]
+\%[\-noapop]
\%[\-kpop]
\%[\-sasl]
\%[\-saslmech\ mechanism]
+\%[\-snoop]
.br
%nmhendpop%
\%[\-version]
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
+\fIinc\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', inc 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 can 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
\fIinc\fR to use Kerberized POP rather than standard POP3 on a given invocation.
If POPSERVICE was also #defined to "kpop", \fIinc\fR will be hardwired to always