5 .TH MSGCHK %manext1% "%nmhdate%" MH.6.8 [%nmhversion%]
7 msgchk \- check for messages
11 .RB [ \-date " | " \-nodate ]
21 .RB [ \-apop " | " \-noapop ]
35 program checks all known mail drops for mail waiting
36 for you. For those drops which have mail for you,
39 indicate if it believes that you have seen the mail in question before.
44 switch indicates under what circumstances
46 should produce a message. The default is
51 should always report the status of the
52 users maildrop. Other values for `type' include `mail' which says that
54 should report the status of waiting mail; and, `nomail'
57 should report the status of empty maildrops.
61 switch has the inverted sense, so
66 to never report the status of
67 maildrops. This is useful if the user wishes to check
69 exit status. A non\-zero exit status indicates that mail was
71 waiting for at least one of the indicated users.
75 produces output, then the
79 to print out the last date mail was read, if this can
85 will normally check all the local mail drops, but if
86 the option \*(lqpophost:\*(rq is set in the mts configuration file
87 \*(lqmts.conf\*(rq, or if the
92 will query this POP service host as to the status of
97 to assume that your account name
98 on the POP server is the same as your current username. To specify
99 a different username, use the `\-user\ username' switch.
101 When using POP, you will normally need to type the password for
102 your account on the POP server, in order to retrieve your messages.
103 It is possible to automate this process by creating a
104 .RI \*(lq \&.netrc \*(rq
105 file containing your login account information for this POP server.
106 For each POP server, this file should have a line of the following
107 form. Replace the words
113 your own account information.
125 .RI \*(lq \&.netrc \*(rq
126 file should be owned and readable only by you.
128 For debugging purposes, there is also a switch
131 allow you to watch the POP transaction take place between you and the
136 has been compiled with APOP support, the
140 to use APOP rather than standard POP3 authentication. Under APOP,
141 a unique string (generally of the format
142 .RI < pid . timestamp @ hostname >)
143 is announced by the POP server.
152 where digest is the MD5 hash of the unique string
153 followed by a `secret' shared by client and server, essentially equivalent to
154 the user's password (though an APOP-enabled POP3 server could have separate APOP
155 and plain POP3 passwords for a single user).
157 disables APOP in cases
158 where it'd otherwise be used.
162 has been compiled with KPOP support, the
166 to use Kerberized POP rather than standard POP3 on a given
169 was also #defined to "kpop",
172 hardwired to always use KPOP.
176 has been compiled with SASL support, the
179 the use of SASL authentication. Depending on the SASL mechanism used, this
180 may require an additional password prompt from the user (but the
181 .RI \*(lq \&.netrc \*(rq
182 file can be used to store this password). The
184 switch can be used to select a particular SASL mechanism.
186 If SASL authentication is successful,
188 will attempt to negotiate
189 a security layer for session encryption. Encrypted traffic is labelled
190 with `(encrypted)' and `(decrypted)' when viewing the POP transaction
199 .ta \w'/usr/local/nmh/etc/ExtraBigFileName 'u
200 ^$HOME/\&.mh\(ruprofile~^The user profile
201 ^%etcdir%/mts.conf~^nmh mts configuration file
202 ^%mailspool%/$USER~^Location of mail drop
205 .SH "PROFILE COMPONENTS"
209 .ta \w'ExtraBigProfileName 'u
218 .RB ` user "' defaults to the current user"
220 .RB ` "\-notify\ all" '