000037631 - Could not connect to message store for POP3 in RSA Identity Governance & Lifecycle

Document created by RSA Customer Support Employee on Jun 13, 2019
Version 1Show Document
  • View in full screen mode

Article Content

Article Number000037631
Applies ToRSA Product Set: Identity Governance & Lifecycle
RSA Version/Condition: 7.x
 
Issue
When  a different account is used for authenticating against the POP3 email server (incoming) than what is used to authenticate against the SMTP email server (outgoing), the connection to the inbound email server fails to connect and the following error is seen in the RSA Identity Governance & Lifecycle User Interface:

 

User-added image



The following error is seen in the aveksaServer.log:
 

javax.mail.MessagingException: Could not connect to message store for pop3://<hostname of pop3 email server>:110;
nested exception is:
javax.mail.AuthenticationFailedException: EOF on socket

 

Please refer to article 000030327 - Artifacts to gather in RSA Identity Governance & Lifecycle to find the location of the aveksaServer.log in your deployment.

CausePOP3 is the inbound email server. Current functionality of RSA Identity Governance & Lifecycle allows authentication of the outbound email server (SMTP), but there is no configuration option to provide authentication credentials to the POP3 email server.
ResolutionThis enhancement has been added to the product starting in RSA Identity Governance & Lifecycle 7.1.1. Because this is considered an enhancement, this functionality will not be back-ported to earlier versions. Please upgrade to 7.1.1 to get this functionality.
WorkaroundUse the same account to authenticate against both the SMTP (outbound) email server and the POP3 (inbound) email server.

Attachments

    Outcomes