Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Authentication Issue in Email Listener when issued from SMA

SA-10136

Summary



User reports that they are not able to start the email listener from System Management Application (SMA).

Error Messages



Listener 'Data-Admin-Connect-EmailListener:TTEmailListener.Listener(com.pega.pegarules.integration.engine.internal.services.email.EmailListener)/0' failed to start because of the following error:
Failed to launch listener, com.pega.pegarules.pub.PRException: Email listener 'Listener.TTEmailListener' failed to connect to Email Server - The server indicated that the authentication credentials for this Email Account are incorrect. From: (B4EEBCEB338356169D30A4B79C67A0CA0:(MBean Access))


Steps to Reproduce



1.Go to SMA >Listener Management
2.Select TTEMailListener and click run
.

Root Cause



The root cause of this problem is software use/operation error.

MS Exchange server always uses TCP port 993 to work with IMAP4 to implement SSL(secured) and due to this user JavaMail props mail.imaps.xxxx.xx props are not getting synced with exchange server connection.


Resolution



The explanation for this behavior is as follows:

Ideally mail.imaps.xxx.xx props must be used for JavaMail if you are using IMAP secured port.

However user tries to access a shared mailbox on MS exchange server and by default it uses IMAP4 protocol (which is IMAP version4).

MS Exchange server always uses TCP port 993 to work with IMAP4 to implement SSL(secured) and due to this your JavaMail props mail.imaps.xxxx.xx props are not getting synced with exchange server connection.

And the above behaviour is specific to MS exchange server unlike other email servers where you can use mail.imaps.xxx props.

Therefore in this case, user is advised to use mail.imap.xxxx.xx props with port 993  to connect securely over IMAP4 protocol which is being used at the exchange server end.

This issue is resolved through the following local-change:

By setting these parameters in Advanced fields of the email account.

("mail.imap.auth.plain.disable", "true");
("mail.imap.auth.ntlm.disable", "true");
("mail.imap.auth.gssapi.disable", "true");

Published June 22, 2015 - Updated October 8, 2020

Was this useful?

100% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice