{
    "content": [
        {
            "type": "text",
            "text": "# msgchk (man)\n\n## NAME\n\nmsgchk - nmh's check for incoming email\n\n## SYNOPSIS\n\nmsgchk [-help] [-version] [-date | -nodate] [-notify all/mail/nomail ] [-nonotify\nall/mail/nomail ] [-host hostname] [-user username] [-sasl | -nosasl] [-saslmech mecha‐\nnism] [-initialtls] [-notls] [-certverify | -nocertverify] [-authservice service]\n[-snoop] [users ... ]\n\n## DESCRIPTION\n\nThe msgchk program checks all known mail drops for mail waiting for  you.   For  those  drops\nwhich  have  mail for you, msgchk will indicate if it believes that you have seen the mail in\nquestion before.\n\n## Sections\n\n- **NAME**\n- **SYNOPSIS**\n- **DESCRIPTION** (2 subsections)\n- **FILES**\n- **PROFILE COMPONENTS**\n- **SEE ALSO**\n- **DEFAULTS**\n- **CONTEXT**\n\nUse structuredContent.sections for detailed options, examples, and full documentation.\n"
        }
    ],
    "structuredContent": {
        "command": "msgchk",
        "section": "",
        "mode": "man",
        "summary": "msgchk - nmh's check for incoming email",
        "synopsis": "msgchk [-help] [-version] [-date | -nodate] [-notify all/mail/nomail ] [-nonotify\nall/mail/nomail ] [-host hostname] [-user username] [-sasl | -nosasl] [-saslmech mecha‐\nnism] [-initialtls] [-notls] [-certverify | -nocertverify] [-authservice service]\n[-snoop] [users ... ]",
        "tldr_summary": null,
        "tldr_examples": [],
        "tldr_source": null,
        "flags": [
            {
                "flag": "",
                "long": null,
                "arg": null,
                "description": "If nmh has been compiled with OAuth support, the -sasl -saslmech xoauth2 switch will enable OAuth authentication. The -user switch must be used, and the user-name must be an email ad‐ dress the user has for the service, which must be specified with the -authservice service switch. Before using this, the user must authorize nmh by running mhlogin and grant autho‐ rization to that account. See the mhlogin man page for more details. If nmh has been compiled with TLS support, the -initialtls switch will require the negotia‐ tion of TLS when connecting to the remote POP server. The -initialtls switch will negotiate TLS immediately after the connection has taken place, before any POP commands are sent or re‐ ceived. Data encrypted by TLS is labeled `(tls-encrypted)' and `(tls-decrypted)` with view‐ ing the POP transaction with the -snoop switch. The -notls switch will disable all attempts to negotiate TLS. 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 -certverify and -nocertverify switches. See your OpenSSL documentation for more information on certificate verification."
            }
        ],
        "examples": [],
        "see_also": [
            {
                "name": "inc",
                "section": "1",
                "url": "https://www.chedong.com/phpMan.php/man/inc/1/json"
            },
            {
                "name": "mh-mail",
                "section": "5",
                "url": "https://www.chedong.com/phpMan.php/man/mh-mail/5/json"
            },
            {
                "name": "post",
                "section": "8",
                "url": "https://www.chedong.com/phpMan.php/man/post/8/json"
            }
        ],
        "section_outline": [
            {
                "name": "NAME",
                "lines": 2,
                "subsections": []
            },
            {
                "name": "SYNOPSIS",
                "lines": 5,
                "subsections": []
            },
            {
                "name": "DESCRIPTION",
                "lines": 16,
                "subsections": [
                    {
                        "name": "Using POP",
                        "lines": 21
                    },
                    {
                        "name": "-snoop",
                        "lines": 17
                    }
                ]
            },
            {
                "name": "FILES",
                "lines": 4,
                "subsections": []
            },
            {
                "name": "PROFILE COMPONENTS",
                "lines": 2,
                "subsections": []
            },
            {
                "name": "SEE ALSO",
                "lines": 2,
                "subsections": []
            },
            {
                "name": "DEFAULTS",
                "lines": 4,
                "subsections": []
            },
            {
                "name": "CONTEXT",
                "lines": 5,
                "subsections": []
            }
        ],
        "sections": {
            "NAME": {
                "content": "msgchk - nmh's check for incoming email\n",
                "subsections": []
            },
            "SYNOPSIS": {
                "content": "msgchk [-help] [-version] [-date | -nodate] [-notify all/mail/nomail ] [-nonotify\nall/mail/nomail ] [-host hostname] [-user username] [-sasl | -nosasl] [-saslmech mecha‐\nnism] [-initialtls] [-notls] [-certverify | -nocertverify] [-authservice service]\n[-snoop] [users ... ]\n",
                "subsections": []
            },
            "DESCRIPTION": {
                "content": "The msgchk program checks all known mail drops for mail waiting for  you.   For  those  drops\nwhich  have  mail for you, msgchk will indicate if it believes that you have seen the mail in\nquestion before.\n\nThe -notify type switch indicates under what circumstances msgchk should produce  a  message.\nThe  default  is  -notify  all  which says that msgchk should always report the status of the\nusers mail drop.  Other values for `type' include `mail' which says that msgchk should report\nthe  status of waiting mail; and, `nomail' which says that msgchk should report the status of\nempty mail drops.  The -nonotify type switch has the inverted sense, so -nonotify all directs\nmsgchk  to never report the status of mail drops.  This is useful if the user wishes to check\nmsgchk's exit status.  A non-zero exit status indicates that mail  was  not  waiting  for  at\nleast one of the indicated users.\n\nIf  msgchk  produces  output, then the -date switch directs msgchk to print out the last date\nmail was read, if this can be determined.\n",
                "subsections": [
                    {
                        "name": "Using POP",
                        "content": "msgchk will normally check all the local mail drops, but if the option “pophost:” is  set  in\nthe  mts configuration file “mts.conf”, or if the -host hostname switch is given, msgchk will\nquery this POP service host as to the status of mail waiting.\n\nTo specify a username for authentication with the POP server, use the -user username  switch.\nThe  credentials  profile  entry in the mh-profile(5) man page describes the ways to supply a\nusername and password.\n\nFor debugging purposes, there is also a switch -snoop, which will allow you to watch the  POP\ntransaction  take  place between you and the POP server.  If -sasl -saslmech xoauth2 is used,\nthe HTTP transaction is also shown.\n\nIf nmh has been compiled with SASL support, the -sasl switch will enable the use of SASL  au‐\nthentication.   Depending on the SASL mechanism used, this may require an additional password\nprompt from the user (but the netrc file can be used to store this password, as described  in\nthe  mh-profile(5)  man  page).  The -saslmech switch can be used to select a particular SASL\nmechanism.\n\nIf SASL authentication is successful, msgchk will attempt to negotiate a security  layer  for\nsession  encryption.  Encrypted traffic is labelled with `(encrypted)' and `(decrypted)' when\nviewing the POP transaction with the -snoop switch; see the  post  man  page  description  of"
                    },
                    {
                        "name": "-snoop",
                        "content": "If  nmh  has been compiled with OAuth support, the -sasl -saslmech xoauth2 switch will enable\nOAuth authentication.  The -user switch must be used, and the user-name must be an email  ad‐\ndress  the  user  has  for the service, which must be specified with the -authservice service\nswitch.  Before using this, the user must authorize nmh by running mhlogin and  grant  autho‐\nrization to that account.  See the mhlogin man page for more details.\n\nIf  nmh  has been compiled with TLS support, the -initialtls switch will require the negotia‐\ntion of TLS when connecting to the remote POP server.  The -initialtls switch will  negotiate\nTLS immediately after the connection has taken place, before any POP commands are sent or re‐\nceived.  Data encrypted by TLS is labeled `(tls-encrypted)' and `(tls-decrypted)` with  view‐\ning  the POP transaction with the -snoop switch.  The -notls switch will disable all attempts\nto negotiate TLS.\n\nWhen using TLS the default is to verify the remote certificate and  SubjectName  against  the\nlocal trusted certificate store.  This can be controlled by the -certverify and -nocertverify\nswitches.  See your OpenSSL documentation for more information on certificate verification.\n"
                    }
                ]
            },
            "FILES": {
                "content": "$HOME/.mhprofile          The user profile\n/etc/nmh/mts.conf          nmh mts configuration file\n/var/mail/$USER            Location of mail drop\n",
                "subsections": []
            },
            "PROFILE COMPONENTS": {
                "content": "None\n",
                "subsections": []
            },
            "SEE ALSO": {
                "content": "inc(1), mh-mail(5) post(8)\n",
                "subsections": []
            },
            "DEFAULTS": {
                "content": "`user' defaults to the current user\n`-date'\n`-notify all'\n",
                "subsections": []
            },
            "CONTEXT": {
                "content": "None\n\n\n\nnmh-1.7.1                                    2016-11-02                                  MSGCHK(1mh)",
                "subsections": []
            }
        }
    }
}