Monitoring an email

[Marc Powell]

> -----Original Message-----
> From: nagios-users-bounces at lists.sourceforge.net [mailto:nagios-users-
> bounces at lists.sourceforge.net] On Behalf Of svalding at kent.edu
> Sent: Monday, August 20, 2007 8:21 AM
> To: Nagios List
> Subject: [Nagios-users] Monitoring an email
> 
> Hey list,
> 
> I've been using nagios for about 6 months now, and am very  pleased
with
> my installation. I've been giving a task, and I'm not sure about how
to
> execute it. I need to make sure that an email goes out every day at
3:00
> pm. This email contains a report of all the orders that have come in
to
> my company during the day. If this email doesn't come out, things get
> backed up, and all hell breaks loose. I was thinking about using the
> check_smtp plugin, but am not quite sure that is the best course of

check_smtp would just verify that your mail server was answering but
provide no specific information about whether a particular e-mail was
processed. If the e-mail is sent or received by a linux box,
check_log2.pl comes to mind. You'd verify in the log file that you saw
the e-mail sent by looking for some unique marker (from=<...> address
for example). While I haven't specifically crafted a time dependent
check, I presume that you could set normal check interval to 24 hours,
and set the check period to something like 3:05 to 3:15 and nagios would
do the right thing.

--
Marc

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null