Not having success using the POP3 alarm acknowledgment feature. I reply back with Pop3AckId:<systemId>:<ackId> copied and pasted directly from the notification email but the alarm is never acknowledged. There are no log messages from alarm.Notification.Email.Pop3AckManager or alarm.Notification.EmailNotificationProfile and no log error messages in general. As a test I changed the <ackId> to a non-exisent(false) value and then get from Pop3AckManager the message, "Pop3 acknoledgement with alarmcode <FalseAckId> not found;skipping acknowledgement." So ignition is reading the inbox and recognizing the acknowledgement syntax, just never acknowledges the alarm when the <ackId> is correct.
FWIW, Pop3AckManager's logging only happens at the debug level. I'd also recommend setting the EmailNotificationProfile logger to trace.
I set both to Debug level, but still no errors and no acknowledgement.
Are you at least seeing a trace level log from EmailNotificationProfile that says something like "Processing msg x of y"? If not, the pop3 server isn't telling Ignition that any messages are available.
I am seeing "Processing msg x of y" and as stated, if I send a non-matching ackId I get the message "Pop3 acknoledgement with alarmcode not found;skipping acknowledgement." logged by Pop3AckManager. That proves that the inbox is being examined for an acknowledgement message.
Yes, that would mean the inbox had something, but the alarm code in the message either was not found or didn't match any alarm codes associated with the user. This doesn't log as an error because Ignition has no way to know if it's an error or not.
If you have a support plan, contacting support would be your best bet.
I figured out the issue and now have the POP acknowledgements working. Through a lot of testing, I determined that the POP ack parser in ignition looks for and requires that the From email address in the ack reply match the To email address that was used during the alarm notification. My application requires that I reply with acknowledgement from a different email than the one I was notified on. My only work around for this was to add my reply acknowledgement email to the same user contact list as the one I receive the notification on. I was then able to acknowledge, as the email I was acknowledging from was also one that received the alarm to begin with.
FYI to you or anybody else - all of the alarm notification methods require that an incoming acknowledge matches contact information assigned to the user that was sent the alarm.
2 Likes
This would be a great note in the documentation. Would have saved me a lot of time
I opened an issue for the docs team about this.
1 Like