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

AuthenticationFailedException occurs on sending email



When using Docker containers to execute the Pega application, error occurs on sending an email in a dynamic container. However, this works correctly in a static container.

Error Messages

(ernal.javamail.JavaEmailClient) DEBUG   Receiver is disconnected
(ernal.javamail.JavaEmailClient) DEBUG  Unable to test email client connectivity due to :535 5.7.3 Authentication unsuccessful

javax.mail.AuthenticationFailedException: 535 5.7.3 Authentication unsuccessful

    at com.sun.mail.smtp.SMTPTransport$Authenticator.authenticate( ~[mail-1.5.5.jar:?]
    at com.sun.mail.smtp.SMTPTransport.authenticate( ~[mail-1.5.5.jar:?]
    at com.sun.mail.smtp.SMTPTransport.protocolConnect( ~[mail-1.5.5.jar:?]

Steps to Reproduce

  1. Configure the Pega application in a Docker container
  2. Configure an email server to use NTLM authentication
  3. Configure an email account with the host name, and username and passwords
  4. Run the Test Connectivity

Root Cause

While loading the Sender profile, it read the protocol, host, and port values. This was entered correctly in the email account rule form. However, while connecting to the Exchange server, error occurred because the IP address of the Docker in the Exchange server was not present in the allow list.


Perform the following local-change:

Add the range of network IP addresses of the Docker in the Exchange server to the allow list.


Published December 2, 2021

Was this useful?

0% 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?

Want to help us improve this content?

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
Contact us