Version

ALL

Date

24 Aug 2004

Summary

Outlook 2000, XP and 2003 can do the ‘optimal’ encoding to the outgoing message.

This modifies the message and could break the automatic event answering by email.

Technical Background

Outlook 2000, XP and 2003 can do the ‘optimal’ encoding to the outgoing message.

Argent uses the keywords “(ANSW:UID=nnnn)”, “(MANT:UID=nnnn)” and “(NOAN:UID=nnnn)” embedded in the message to identify which event should be answered.

Unfortunately, Outlook clients can arbitrarily encode the ‘=’ into ‘=3D’ using its own logic.

It corrupts the raw message text the Argent Console engine searches.

In the engine log, we could see messages like

Mon Aug 23 13:20:22.173 KYPHONGUARD Svc_Guardian Failed to find console record with Unique Id=3.

Alert answering is not processed

Resolution

To address this Microsoft specific issue, change the keywords in the email alert definition as follows:

Original Keywords	New Keywords
(ANSW:UID=%AGUniqueID%)	(ANSW:UID .EQ. %AGUniqueID%)
(MANT:UID=%AGUniqueID%)	(MANT:UID .EQ. %AGUniqueID%)
(NOAN:UID=%AGUniqueID%)	(NOAN:UID .EQ. %AGUniqueID%)