The basic function of this check is to log in into an IMAP or POP3 mailbox to monitor whether or not the login is possible. An extended feature is, that the check can fetch all (or just some) from the mailbox and forward them as events to the Event Console.
Step-by-step guide
- WATO - CONFIGURATION → Host & Service Parameters → Active checks → Check Email
CHECK EMAIL
Service description: Here you can type in a service description. Please make sure that this is unique per host and does not collide with other services.
Mail Receiving: Here you can select if you want to check your IMAP or POP3 login. You need your login credentials for your E-Mail Mailbox.
Forward mails as events to Event Console.
Forwarding Method: Here you can select if you want to send the events either to the EC or to a remote syslog host. If you want to send the events to the local EC, we would recommend using the spooling mechanism.
By using the spooling mechanism, the check will store all collected eventsin one file in ~/var/mkeventd/spool.OMD[nagnis_master]:~$ ll ~/var/mkeventd/spool/ total 3600 -rw-rw---- 1 nagnis_master nagnis_master 79124 Dec 7 15:36 localhost_407343_1607351778 -rw-rw---- 1 nagnis_master nagnis_master 79124 Dec 7 15:37 localhost_408329_1607351841
Only process mails with matching subject: Use this option to not process all messages found in the inbox, but only the those whose subject matches the given regular expression. The text entered here is handled as a regular expression pattern. The pattern is matched from the beginning. Add a tailing $ to change it to a whole text match. The match is performed case sensitive. Read more about regular expression matching in Checkmk in our user manual.
Events: Syslog facility: Use this syslog facility for all created events
Events: Hostname: Use this hostname for all created events instead of the name of the mailserver
Limit length of mail body: When forwarding mails from the mailbox to the event console, the body of the mail is limited to the given number of characters.
Cleanup messages: The handled messages (see subject matching) can be cleaned up by either deleting them or moving them to a subfolder. By default nothing is cleaned up.
Debugging
EC Log
In the log of the EC you can see the processing messages from the spool file:
2020-12-07 12:51:18,078 [20] [cmk.mkeventd.EventServer] Processing message '<21>Dec 7 12:51:17 localhost Checkmk EC: Checkmk EC|Email to EC of Checkmk!' 2020-12-07 12:51:18,079 [20] [cmk.mkeventd.EventServer] Parsed message: application: Checkmk EC core_host: facility: 2 host: localhost host_in_downtime: False ipaddress: pid: 0 priority: 5 text: Checkmk EC|Email to EC of Checkmk! time: 1607341877.0
Execute active Check manually
For debugging reasons it could be useful to run the check manually. Therefore, you need to open the service site of the E-Mail service and search for 'Service check command'. Now you can use the command for executing the check manually.
OMD[nagnis_master]:~/lib/nagios/plugins$ ./check_mail --pwstore=6@11@strato '--protocol=IMAP' '--server=imap.provider.de' '--ssl' '--port=993' '--username=mail@provider.de' '--password=*************' '--forward-ec' '--forward-method=spool:' '--match-subject=Checkmk EC' '--forward-facility=2' '--forward-host=localhost' '--cleanup=delete' OK - Forwarded 0 messages to event console | messages=0
For a detailed log you can use --debug at the end of the command:
OMD[nagnis_master]:~$ ~/lib/nagios/plugins/check_mail --pwstore=6@11@strato '--protocol=IMAP' '--server=imap.provider.de' '--ssl' '--port=993' '--username=mail@provider.de' '--password=*************' '--forward-ec' '--forward-method=spool:' '--match-subject=Checkmk EC' '--forward-facility=2' '--forward-host=localhost' '--cleanup=delete' --debug
For more information you can use --help
~/lib/nagios/plugins/check_mail -h
The Event would look like this:
Related articles
Filter by label
There are no items with the selected labels at this time.