I thought of that and had a quick look around. I logged into the the MTA on Nagios via Telnet and was able to successfully send mail so I know that mail is capable of being sent. Nagios is also having no trouble sending some critical alerts. The weird thing for me is that if the messages were being stopped at the MTA level or by the relaying server then I would think that Nagios’ Notification log would still show that it attempted to send them. At this point there is no indication that Nagios even tried to send out a notification.
From: sascha.runsc...@gfkl.com [mailto:sascha.runsc...@gfkl.com] Sent: Friday, July 24, 2009 3:16 AM To: Nagios User List Subject: [Nagios-users] Antwort: Notification oddity > I’ve checked my Contacts, as well as my Host and Service > notifications entries and all are configured W,U,C,R for 24x7. I’ve > even done some work on Nagios today and restarted to load in some > new stuff, but I’m still not seeing anything other than Critical > notifications. > > Clearly I’m missing something. I would appreciate any advice. Did you check the MTAs - local and the relay? Maybe the relay you are using started ditching your mails because of some strange anti-spam or maybe your host got throttled by the mailserver because it was sending too much mails. Just an idea, but I've seen strange setups of "local relays" being Exchange or Domino servers with really stupid policies ;) S GFKL Financial Services AG Vorstand: Dr. Peter Jänsch (Vors.), Jürgen Baltes, Dr. Tom Haverkamp Vorsitzender des Aufsichtsrats: Dr. Georg F. Thoma Sitz: Limbecker Platz 1, 45127 Essen, Amtsgericht Essen, HRB 13522 No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.5.392 / Virus Database: 270.13.26/2257 - Release Date: 07/23/09 18:00:00
------------------------------------------------------------------------------
_______________________________________________ Nagios-users mailing list Nagios-users@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