###############################################################################
#
# Contact Group configuration file
#
# Created by: Nagios QL Version 3.0.3
# Date: 2011-11-03 09:46:10
# Version: Nagios 3.x config file
#
# --- DO NOT EDIT THIS FILE BY HAND ---
# Nagios QL will overwite all manual settings during the next update
#
###############################################################################
define contactgroup {
contactgroup_name admins
alias Nagios Administrators
members nagiosadmin
}
define contactgroup {
contactgroup_name xi_contactgroup_all
alias All Contacts
}
###############################################################################
#
# Contact Group configuration file
#
# END OF FILE
#
###############################################################################
I didn't see anything "unusual" in the config files - they look fine. In my opinion, if nagios can send a test e-mail to one address and can't send it to another, most probably you will have to look at your network. Not sure what's going on.
Be sure to check out our Knowledgebase for helpful articles and solutions!
Strange occurrence when testing this. We figured out that an IronPort appliance was blacklisting Nagios. I sent test notifications and the mobile text was received, but the email was not. Any ideas why that might happen?
I am not familiar with IronPort but I would guess that Nagios could've been blocked if considered to be a "high volume sender". I found this document, explaining how to configure IronPort's Safe/Block lists. Again, I am not familiar and I don't know if this will help.
One more thing...is there a default in nagios to use an event handler? I noticed in the templates that there is no event handler defined. Could that be the catch here?
I *think* that by default all state changes use the global event handler "xi_host_event_handler" and "xi_service_event_handler". However you can define specific event handlers at the template, host, and service level as well in addition to the global event handler.
I did some back tracking and it looks like the proper event handler is inherited from a previous template. I also ran another test by replaced the admin email with my own and I received notifications regularly again. After a brief discussion with the tech in charge of IronPort, I guess he's starting from scratch on the email blacklisting issue so hopefully I'll have better luck. Would it make a difference if the sending email is the same as the receiving email? For example, if the admin email is [email protected] and the alerts are getting sent from [email protected] to [email protected], will that cause an issue in alerting? I can send myself emails from my own email address so I wouldn't think this would cause a problem but I wanted to confirm with you first.