4 .TH MSGCHK %manext1% "%nmhdate%" MH.6.8 [%nmhversion%]
6 msgchk \- check for messages
11 .RB [ \-date " | " \-nodate ]
21 .RB [ \-apop " | " \-noapop ]
36 program checks all known mail drops for mail waiting
37 for you. For those drops which have mail for you,
40 indicate if it believes that you have seen the mail in question before.
45 switch indicates under what circumstances
47 should produce a message. The default is
52 should always report the status of the
53 users maildrop. Other values for `type' include `mail' which says that
55 should report the status of waiting mail; and, `nomail'
58 should report the status of empty maildrops.
62 switch has the inverted sense, so
67 to never report the status of
68 maildrops. This is useful if the user wishes to check
70 exit status. A non\-zero exit status indicates that mail was
72 waiting for at least one of the indicated users.
76 produces output, then the
80 to print out the last date mail was read, if this can
86 will normally check all the local mail drops, but if
87 the option \*(lqpophost:\*(rq is set in the mts configuration file
88 \*(lqmts.conf\*(rq, or if the
93 will query this POP service host as to the status of
98 to assume that your account name
99 on the POP server is the same as your current username. To specify
100 a different username, use the `\-user\ username' switch.
102 When using POP, you will normally need to type the password for
103 your account on the POP server, in order to retrieve your messages.
104 It is possible to automate this process by creating a
105 .RI \*(lq \&.netrc \*(rq
106 file containing your login account information for this POP server.
107 For each POP server, this file should have a line of the following
108 form. Replace the words
114 your own account information.
126 .RI \*(lq \&.netrc \*(rq
127 file should be owned and readable only by you.
129 For debugging purposes, there is also a switch
132 allow you to watch the POP transaction take place between you and the
137 has been compiled with APOP support, the
141 to use APOP rather than standard POP3 authentication. Under APOP,
142 a unique string (generally of the format
143 .RI < pid . timestamp @ hostname >)
144 is announced by the POP server.
153 where digest is the MD5 hash of the unique string
154 followed by a `secret' shared by client and server, essentially equivalent to
155 the user's password (though an APOP-enabled POP3 server could have separate APOP
156 and plain POP3 passwords for a single user).
158 disables APOP in cases
159 where it'd otherwise be used.
163 has been compiled with KPOP support, the
167 to use Kerberized POP rather than standard POP3 on a given
170 was also #defined to "kpop",
173 hardwired to always use KPOP.
177 has been compiled with SASL support, the
180 the use of SASL authentication. Depending on the SASL mechanism used, this
181 may require an additional password prompt from the user (but the
182 .RI \*(lq \&.netrc \*(rq
183 file can be used to store this password). The
185 switch can be used to select a particular SASL mechanism.
187 If SASL authentication is successful,
189 will attempt to negotiate
190 a security layer for session encryption. Encrypted traffic is labelled
191 with `(encrypted)' and `(decrypted)' when viewing the POP transaction
200 .ta \w'%etcdir%/ExtraBigFileName 'u
201 ^$HOME/\&.mh\(ruprofile~^The user profile
202 ^%etcdir%/mts.conf~^nmh mts configuration file
203 ^%mailspool%/$USER~^Location of mail drop
206 .SH "PROFILE COMPONENTS"
210 .ta \w'ExtraBigProfileName 'u
219 .RB ` user "' defaults to the current user"
221 .RB ` "\-notify\ all" '