NotifyPI – Exacq

Description

A NotifyPI enhancement was released with 8.4 which added the ability to specify ‘when’ to send an email: ‘Alarm Starts’, ‘Alarm Ends’ or ‘Alarm Starts and Ends’). However, the ‘Alarm Ends’ selection was failing to send the email when the trigger event (alarm) duration was shorter than the ‘Send Rate Limit’.
If the event duration was longer than ‘Send Rate Limit’, the email was sent as expected.

Version introduced

8.4

Platforms

All

Steps to reproduce

* Configure a Notifications email server
* Configure a Notifications email profile
– Alarm Ends
– Send Rate Limit 10
* Configure a new ‘Event Linking’ entry
– Soft Trigger
– – new trigger
– Action Type: Notify
– Action Target: the email profile
* Set, then within 10 seconds, clear the Soft Trigger

Expected result

Expect to receive an email

Actual result

No email was sent

Workaround

* Create an event Source Group
– Add the Soft Trigger
– Select ‘Any source’
– Select ‘When not alarmed’
– Modify the Notification email profile ‘When’ to ‘Alarm Starts’

Problem:

Server logs resemble:

15/12/2016 2:54:54 PM NotifyPI Warning Profile Description: Playground. Notification attempt return code= 55 15/12/2016 2:54:54 PM NotifyPI Verbose curl: (55) MAIL failed: 530 15/12/2016 2:54:54 PM NotifyPI Error Failed to send notification using profile Playground. This message will be retried

This is caused by missing data from compliance with RFC5321. This will cause failure with some SMTP servers, but not others, depending on how they accommodate the message.