Broadcasting issue 'Could not convert socket to TLS'

Dylan Verhagen shared this problem 13 days ago
Awaiting Reply

Dear support,

Since a week or two we started getting broadcast failures with the error 'Error sending email: javax.mail.MessagingException: Could not convert socket to TLS;

nested exception is:

javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake

javax.mail.MessagingException: Could not convert socket to TLS;'


The strange thing is that this seems to happen randomly since most other broadcasts seem to work just fine.

We're currently using an Office365 email to broadcast the reports and our vendor put forward the idea that it might had to do with an old version of TLS (1.0/1.1).

I came across one of your articles explaining how to force TLS 1.2 (https://community.yellowfinbi.com/knowledge-base/article/how-to-connect-to-a-mail-server-that-forces-tls-1-2) but am having issues with step 1.

How do I 'ensure' that we're using 'javax.mail-1.6.2.jar'?

I've done all the other steps but according to the mail log it's still using 'javamail-1.5.2.jar'. I added a part of the mail log (with debugging on), hopefully you can point me in the right direction to get this issue resolved.

Regards,

Dylan

Comments (2)

photo
1

Hi Dylan,


Thanks for your question.


Would you mind clarifying what you've done for the first step? My understanding here is that you will need delete any other javax.mail dependencies that are present in the lib folder, and replace them with the 1.6.2 version.


Then, you would need to follow the remainder of the steps and then restart the Yellowfin service.


Are you able to confirm that you've done this?


Kind regards,

Simon

photo
1

Hi Dylan,


I just wanted to check in to see how you are traveling with this issue.


Please let me know if you have any further questions and I'll get back to you shortly.


Otherwise, I will go ahead and mark this as answered.


Kind regards,

Simon