Monitor Email...
jmoseley at corp.xanadoo.com
jmoseley at corp.xanadoo.com
Wed Jan 21 20:36:24 CET 2009
You're probably going to have to write this yourself. Sounds like an
excellent opportunity for a perl/expect plugin. ;-)
James Moseley
Matt Nelson
<matt at frozenatom.
com> To
Nagios Users Mailinglist
01/21/2009 12:51 <nagios-users at lists.sourceforge.net
PM >
cc
Subject
[Nagios-users] Monitor Email...
We are working on migrating off of Sitescope... <insert reasons here>...
Anyways We have almost got all of the services working, but I have not
found one yet to replace:
"External Email Loop Monitor"
Here are the details of this monitor:
"The SiteScope Mail Monitor checks a Mail Server via the network. It
verifies that the mail server is accepting requests, and also verifies that
a message can be sent and retrieved. It does this by sending a standard
mail message using SMTP and then retrieving that same message via a POP
user account. Each message that SiteScope sends includes a unique key which
it checks to insure that it does not retrieve the wrong message and return
a false OK reading. If SiteScope is unable to complete the entire loop it
generates an error message.
Each time the Mail Monitor runs, it returns a status and writes it in the
<SiteScope install path>/SiteScope/logs/SiteScope.log file. It also writes
the total time it takes to send and receive the mail message in the log
file."
Anyone know of a current monitor to replace this?
------------------------------------------------------------------------------
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
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
More information about the Users
mailing list