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

Email sending issue (530 5.7.1 Authentication required)



User needs to send emails from their PRPC system through a highly secured SMTP MTA. But when connecting to that MTA from PRPC, they are getting errors like mentioned below.

Error Messages

com.sun.mail.smtp.SMTPSendFailedException: 530 5.7.1 Authentication required

and after moving to Java 8:

2016-07-18 12:44:10,187 [p-bio-8443-exec-1716] [ STANDARD] [ EPS:01.01.01]
(pega_integrationengine_default) ERROR|###.###.###.### user -
Unexpected exception caught while trying to send an email message.
javax.mail.MessagingException: Could not convert socket to TLS;
nested exception is: Remote host closed connection during handshake
at com.sun.mail.smtp.SMTPTransport.startTLS(
at com.sun.mail.smtp.SMTPTransport.protocolConnect(
at javax.mail.Service.connect(
at javax.mail.Service.connect(
at java.util.concurrent.ThreadPoolExecutor$
Caused by: Remote host closed connection during
at com.sun.mail.util.SocketFetcher.configureSSLSocket(
at com.sun.mail.util.SocketFetcher.startTLS(
at com.sun.mail.smtp.SMTPTransport.startTLS(
... 82 more
Caused by: SSL peer shut down incorrectly
... 88 more
2016-07-18 12:44:10,191 [p-bio-8443-exec-1716] [ STANDARD] [ EPS:01.01.01]
(pega_integrationengine_default) ERROR|###.###.###.### user -
Failing message has sender ID of <[email protected]> and addressee of
<[email protected]>.

Steps to Reproduce

To reproduce the issue, the SMTP MTA needs to be configured in a special way; in particular, it has to use certificates and encryption keys longer than 1024 bits.

No special setup for PRPC is needed, other than the well document configuration for outbound email. The customer did not reveal the detailed configuration of their SMTP MTA to us.

Root Cause

The root cause was a well known shortcoming in Java 7, in the area of encryption, and a bug in JavaMail, version 1.5.2, that was related to the Java 7 issue mentioned before. In Java 8, the shortcoming was repaired, and the bug in JavaMail was removed with version 1.5.3 of that library.


As the root cause description indicates, the solution has two steps:

1. Upgrade the underlying JVM to Java 8.
2. Replace the JavaMail 1.5.2 library by the latest one, version 1.5.5.

The latter is provided with the HFix-28762.

Published August 24, 2016 - Updated October 8, 2020

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