Support Article
AuthenticationFailedException occurs on sending email
SA-90808
Summary
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(SMTPTransport.java:914) ~[mail-1.5.5.jar:?]
at com.sun.mail.smtp.SMTPTransport.authenticate(SMTPTransport.java:825) ~[mail-1.5.5.jar:?]
at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:730) ~[mail-1.5.5.jar:?]
Steps to Reproduce
- Configure the Pega application in a Docker container
- Configure an email server to use NTLM authentication
- Configure an email account with the host name, and username and passwords
- 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.
Resolution
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
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.