Email approvals from Outlook desktop result in "reply could not be understood" in RSA Identity Governance & Lifecycle
Originally Published: 2020-09-22
Article Number
Applies To
RSA Version/Condition: 7.1.1, 7.2.0, 7.2.1
Issue
aveksaServer.log records error messages similar to the following:
05/01/2020 14:00:27.566 ERROR (ApprovalInboxProcessorServiceProvider) [com.aveksa.server.email.mailboxmonitor.ApprovalInboxProcessorServiceProvider] Failed to send response to user informing them that their reply was not parsable. Message Details=05/01/2020 14:00:27.566 ERROR (ApprovalInboxProcessorServiceProvider) [com.aveksa.server.email.mailboxmonitor.ApprovalInboxProcessorServiceProvider] Failed to send response to user informing them that their reply was not parsable. Message Details=FROM: "Smith, John" <JSmith@aveksa.com>REPLY TO: "Smith, John" <JSmith@aveksa.com>TO: =?Windows-1252?Q?GM_=96_Access_Approvals?= <access-approvals@aveksa.com>Subject: RE:Identity & Access - 14798 - Approval Required <AV-22275-REF>SendDate: Fri May 01 13:45:51 UTC 2020\AnsweredCONTENT-TYPE: text/html; charset=Windows-1252---------------------------
java.lang.NullPointerException at com.aveksa.server.email.common.EmailUtils.guessContentType(EmailUtils.java:665) at com.aveksa.server.email.mailboxmonitor.ApprovalInboxProcessorServiceProvider.sendEmailResponse(ApprovalInboxProcessorServiceProvider.java:556) at com.aveksa.server.email.mailboxmonitor.ApprovalInboxProcessorServiceProvider.sendEmailResponse(ApprovalInboxProcessorServiceProvider.java:466) at com.aveksa.server.email.mailboxmonitor.ApprovalInboxProcessorServiceProvider.handleCouldNotParseEmail(ApprovalInboxProcessorServiceProvider.java:740) at com.aveksa.server.email.mailboxmonitor.ApprovalInboxProcessorServiceProvider.emailArrived(ApprovalInboxProcessorServiceProvider.java:1051) at com.aveksa.server.email.mailboxmonitor.MailboxMonitorThread.checkForMail(MailboxMonitorThread.java:186) at com.aveksa.server.email.mailboxmonitor.MailboxMonitorThread.run(MailboxMonitorThread.java:52)
When replying from Outlook Web Access (OWA), the emails are understood and parsed correctly.
Cause
This issue occurs with email replies sent from Microsoft Outlook version 12527.208880 and later.
Outlook email in HTML format separates the Action:Accept verb from the comments by an HTML <BR> tag instead of a new line.
Resolution
- RSA Identity Governance & Lifecycle 7.1.1 P11
- RSA Identity Governance & Lifecycle 7.2.0 P05
- RSA Identity Governance & Lifecycle 7.2.1 P01
Related Articles
Enable Email Reply Processing options differ in approval node in RSA Identity Governance & Lifecycle 35Number of Views In RSA Identity Governance and Lifecycle, the Vaild Reply Answers are not displayed in the Approval Request email. 125Number of Views RSA Authenticator 6.2 for Windows Quick Start Guide (German) 26Number of Views DLP Guide to understanding what the various error conditions mean in the data scan report 96Number of Views Windows desktop machine does not display last logged in user ID with RSA Authentication Agent 7.x for Microsoft Windows 73Number of Views
Trending Articles
How to recover the Application and AFX after an unexpected database failure in RSA Identity Governance & Lifecycle Troubleshooting AFX Connector issues in RSA Identity Governance & Lifecycle RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA Release Notes for RSA Authentication Manager 8.8 RSA Authentication Manager Upgrade Process
Don't see what you're looking for?