.\"
.\" %nmhwarning%
-.\" $Id$
.\"
.TH INC %manext1% "%nmhdate%" MH.6.8 [%nmhversion%]
.SH NAME
.RB [ \-nopack ]
.RB [ \-proxy
.IR command ]
-.RB [ \-apop " | " \-noapop ]
-.RB [ \-kpop ]
.RB [ \-sasl ]
.RB [ \-saslmech
.IR mechanism ]
.PP
.RS 5
.nf
-\*(<<inc\*(>> date
+<<inc>> date
<scan line for first message>
<scan line for second message>
<etc.>
.PP
If
.B nmh
-has been compiled with APOP support, the
-.B \-apop
-switch will cause
-.B inc
-to use APOP rather than standard POP3 authentication. Under APOP, a
-unique string (generally of the format
-.RI < pid . timestamp @ hostname >
-) is announced by the POP server.
-Rather than `USER
-.IR user ',
-`PASS
-.IR password ',
-.B inc
-sends `APOP
-.I user
-.IR digest ',
-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).
-.B \-noapop
-disables APOP in cases where it'd otherwise be used.
-.PP
-If
-.B nmh
-has been compiled with KPOP support, the
-.B \-kpop
-switch will allow
-.B inc
-to use Kerberized POP rather than standard POP3 on a given invocation.
-If POPSERVICE was also #defined to "kpop",
-.B inc
-will be hardwired to always use KPOP.
-.PP
-If
-.B nmh
has been compiled with SASL support, the
.B \-sasl
switch will enable