-.TH MSGCHK %manext1% "November 25, 2014" "%nmhversion%"
-.\"
+.TH MSGCHK %manext1% 2016-11-02 "%nmhversion%"
+.
.\" %nmhwarning%
-.\"
+.
.SH NAME
msgchk \- check for messages
.SH SYNOPSIS
.HP 5
.na
.B msgchk
+.RB [ \-help ]
+.RB [ \-version ]
.RB [ \-date " | " \-nodate ]
.RB [ \-notify
all/mail/nomail ]
.IR hostname ]
.RB [ \-user
.IR username ]
-.RB [ \-sasl ]
+.RB [ \-sasl " | " \-nosasl ]
.RB [ \-saslmech
.IR mechanism ]
-.RB [ \-oauth
+.RB [ \-initialtls ]
+.RB [ \-notls ]
+.RB [ \-certverify " | " \-nocertverify ]
+.RB [ \-authservice
.IR service ]
.RB [ \-snoop ]
.RI [ users
\&... ]
-.RB [ \-version ]
-.RB [ \-help ]
.ad
.SH DESCRIPTION
The
which says that
.B msgchk
should always report the status of the
-users maildrop. Other values for `type' include `mail' which says that
+users mail drop. Other values for `type' include `mail' which says that
.B msgchk
should report the status of waiting mail; and, `nomail'
which says that
.B msgchk
-should report the status of empty maildrops.
+should report the status of empty mail drops.
The
.B \-nonotify
.I type
directs
.B msgchk
to never report the status of
-maildrops. This is useful if the user wishes to check
+mail drops. This is useful if the user wishes to check
.BR msgchk 's
-exit status. A non\-zero exit status indicates that mail was
-.B not
+exit status. A non-zero exit status indicates that mail was
+.I not
waiting for at least one of the indicated users.
.PP
If
which will
allow you to watch the POP transaction take place between you and the
POP server. If
-.B \-oauth
+.B \-sasl \-saslmech xoauth2
is used, the HTTP transaction is also shown.
.PP
If
with `(encrypted)' and `(decrypted)' when viewing the POP transaction
with the
.B \-snoop
-switch.
+switch; see the
+.B post
+man page description of
+.B \-snoop
+for its other features.
.PP
If
.B nmh
has been compiled with OAuth support, the
-.B \-oauth
+.B \-sasl \-saslmech xoauth2
switch will enable OAuth authentication. The
.B \-user
switch must be used, and the
.I user-name
-must be an email address the user has for that service. Before using this,
-the user must authorize nmh by running
+must be an email address the user has for the service, which must
+be specified with the
+.B \-authservice
+.I service
+switch. Before using this, the user must authorize nmh by running
.B mhlogin
-and grant authorization to that account. Only
-.B -oauth
-.I gmail
-is supported. See the
+and grant authorization to that account. See the
.B mhlogin
man page for more details.
.PP
-Gmail only supports POP3 over TLS, but
-.B msgchk
-has no TLS support. To work around this, use something like
-.B -proxy 'openssl s_client -connect %h:995 -CAfile /etc/ssl/certs/ca-certificates.crt -quiet'
+If
+.B nmh
+has been compiled with TLS support, the
+.B \-initialtls
+switch will require the negotiation of TLS when connecting
+to the remote POP server. The
+.B \-initialtls
+switch will negotiate TLS immediately after the connection has taken place,
+before any POP commands are sent or received. Data encrypted by TLS is
+labeled `(tls-encrypted)' and `(tls-decrypted)` with viewing the POP
+transaction with the
+.B \-snoop
+switch. The
+.B \-notls
+switch will disable all attempts to negotiate TLS.
+.PP
+When using TLS the default is to verify the remote certificate and SubjectName
+against the local trusted certificate store. This can be controlled by
+the
+.B \-certverify
+and
+.B \-nocertverify
+switches. See your OpenSSL documentation for more information on certificate
+verification.
.SH FILES
.fc ^ ~
.nf
.ta \w'%nmhetcdir%/ExtraBigFileName 'u
-^$HOME/\&.mh\(ruprofile~^The user profile
+^$HOME/.mh_profile~^The user profile
^%nmhetcdir%/mts.conf~^nmh mts configuration file
^%mailspool%/$USER~^Location of mail drop
.fi
.SH "SEE ALSO"
.IR inc (1),
.IR mh\-mail (5)
+.IR post (8)
.SH DEFAULTS
.nf
.RB ` user "' defaults to the current user"
projects / nmh / blobdiff