Ad Widget

Collapse

Email notifications 'break' in 1.6.5

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • tommyj27
    Junior Member
    • Mar 2010
    • 2

    #1

    Email notifications 'break' in 1.6.5

    (2nd attempt, got timed out of the forum)

    I have been trying to sort out a problem with my zabbix system for several days where zabbix appears to stop sending email notifications to certain recipients (possibly caused by multiple failures?). I am running zabbix 1.6.5 installed from the Debian squeeze repos.

    A little background. I have a number of alerts configured that send email to multiple recipients including my office inbox and my cell phone. My office email is always received, but delivery to my cell phone keeps stopping.

    The audit action logs do not indicate that the cell phone delivery was even attempted. My initial thought was that my mail might be getting lost on my cell carrier's network, since I have a separate Media Type configured that delivers directly to my cell carrier's smtp server. However, traffic dumps confirmed that zabbix was not even attempting to send. Strangely, I tried creating a duplicate media type for zabbix to send to my cell and this worked for several days.

    Most recently, I have created a new media type that sends email to localhost (allowing postfix running on the machine to handle the final delivery). I configured zabbix to send my work email and cell email though this media type. The result is that my work email is delivered reliably, but the postfix logs do not even show zabbix attempt delivery for my cell.

    The email stoppage has occurred after several alerts failed to send to my cell (due to Internet connectivity issues). Is it possible that zabbix decides that it cannot send to a particular email address, and never tries again?

    Thanks
  • tommyj27
    Junior Member
    • Mar 2010
    • 2

    #2
    I think I have sorted out my problem, or at least my latest manifestation of it. In all my messing around, I must have changed my cell phone user to a standard user. Changing it back to a super admin resolved the problem.

    Comment

    Working...