We're having a problem with Sprint's email-to-pager gateway will refuse connections and defer messages with the response "Too many connections from host" when Nagios is trying to alert all of us at once that something has failed. Obviously, since we don't know it's happening unless we're in the office, this isn't necessarily a good thing -- the person who really needs to respond might not get their notification for minutes or hours, and in the meantime, the service is down.
We've found that if we send messages with a 5-second gap, Sprint doesn't complain about us spamming their gateway. Is there a way to get Nagios (or alternately the MTA, which I realize would be off-topic, but I'm not a MTA guy) to stagger out the notifications --without some arcane hack like using escalations? Thanks, Karl Katzke TAMU RGS ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Nagios-users mailing list [email protected] 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
