5 .TH MSGCHK %manext1% "%nmhdate%" MH.6.8 [%nmhversion%]
7 msgchk \- check for messages
12 .RB [ \-date " | " \-nodate ]
22 .RB [ \-apop " | " \-noapop ]
37 program checks all known mail drops for mail waiting
38 for you. For those drops which have mail for you,
41 indicate if it believes that you have seen the mail in question before.
46 switch indicates under what circumstances
48 should produce a message. The default is
53 should always report the status of the
54 users maildrop. Other values for `type' include `mail' which says that
56 should report the status of waiting mail; and, `nomail'
59 should report the status of empty maildrops.
63 switch has the inverted sense, so
68 to never report the status of
69 maildrops. This is useful if the user wishes to check
71 exit status. A non\-zero exit status indicates that mail was
73 waiting for at least one of the indicated users.
77 produces output, then the
81 to print out the last date mail was read, if this can
87 will normally check all the local mail drops, but if
88 the option \*(lqpophost:\*(rq is set in the mts configuration file
89 \*(lqmts.conf\*(rq, or if the
94 will query this POP service host as to the status of
99 to assume that your account name
100 on the POP server is the same as your current username. To specify
101 a different username, use the `\-user\ username' switch.
103 When using POP, you will normally need to type the password for
104 your account on the POP server, in order to retrieve your messages.
105 It is possible to automate this process by creating a
106 .RI \*(lq \&.netrc \*(rq
107 file containing your login account information for this POP server.
108 For each POP server, this file should have a line of the following
109 form. Replace the words
115 your own account information.
127 .RI \*(lq \&.netrc \*(rq
128 file should be owned and readable only by you.
130 For debugging purposes, there is also a switch
133 allow you to watch the POP transaction take place between you and the
138 has been compiled with APOP support, the
142 to use APOP rather than standard POP3 authentication. Under APOP,
143 a unique string (generally of the format
144 .RI < pid . timestamp @ hostname >)
145 is announced by the POP server.
154 where digest is the MD5 hash of the unique string
155 followed by a `secret' shared by client and server, essentially equivalent to
156 the user's password (though an APOP-enabled POP3 server could have separate APOP
157 and plain POP3 passwords for a single user).
159 disables APOP in cases
160 where it'd otherwise be used.
164 has been compiled with KPOP support, the
168 to use Kerberized POP rather than standard POP3 on a given
171 was also #defined to "kpop",
174 hardwired to always use KPOP.
178 has been compiled with SASL support, the
181 the use of SASL authentication. Depending on the SASL mechanism used, this
182 may require an additional password prompt from the user (but the
183 .RI \*(lq \&.netrc \*(rq
184 file can be used to store this password). The
186 switch can be used to select a particular SASL mechanism.
188 If SASL authentication is successful,
190 will attempt to negotiate
191 a security layer for session encryption. Encrypted traffic is labelled
192 with `(encrypted)' and `(decrypted)' when viewing the POP transaction
201 .ta \w'%etcdir%/ExtraBigFileName 'u
202 ^$HOME/\&.mh\(ruprofile~^The user profile
203 ^%etcdir%/mts.conf~^nmh mts configuration file
204 ^%mailspool%/$USER~^Location of mail drop
207 .SH "PROFILE COMPONENTS"
211 .ta \w'ExtraBigProfileName 'u
220 .RB ` user "' defaults to the current user"
222 .RB ` "\-notify\ all" '