IFS 9/10 TLS1.2 smtp.office365

Hi @paguin ,

Normally, TLS1.2 is supported for office365 

Have you tried to do telnet to smtp.office365.com and on port : 587 from the IFS server to check if you are able to connect it outside IFS application? If yes, perhaps you can check the security protocol and it should be SMTP+STARTTLS 

Regards,

Anil

@Anil Dubey ,

thanks for your response. i am able to telnet to smtp host with port 587.

But still i am getting error 

Error while sending data... 
Caused by: javax.mail.MessagingException: Could not convert socket to TLS 
Caused by: javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake 
Caused by: java.io.EOFException: SSL peer shut down incorrectly

Any further solutions are welcome

regards

Pankaj

@paguin 

I think there could be several areas of concerns which you will have to check in order to fix this issue. To fix it faster, I suggest that you will have to open IFS case to get R&D attention + a case with Microsoft office 365 team

you will have check when this issue started and what changes has been done before that. Possible reasons could be :

=> Disabling of TLS1.0 and TLS 1.1  (but it has been ongoing for past 2 years but it depends if you were still on TLS 1.0 or 1.1)

Disabling TLS 1.0 and 1.1 for Microsoft 365 | Microsoft Learn

Preparing for TLS 1.2 in Office 365 and Office 365 GCC | Microsoft Learn

=> SSL Certificate issue 

Regards,

Anil

Hi Team, Do we find any solution for this

@surenswo 

nops 

tried all what was possible 

any one who can help here …

Regards

Pankaj

@paguin 

Hi Pankaj,

Have you found a solution for this? or have you already dispatched a case to IFS?

Best Regards,
Hashan

There are other community posts that might be interesting for TLS1.2

Enabling TLS 1.2 support in IFS Apps9 | IFS Community or
New opt-in endpoint available for SMTP AUTH clients still needing legacy TLS - Microsoft Community Hub

One of our customers is facing the “Could not convert socket to TLS” issue and hopefully updating to TLS1.2 and removing TLS1.0 and TLS1.1 by reconfiguring the environment will solve the issue

Best regards,
  Stefan

Hello @FLESTEFAN ,

None of these solutions worked. 

https://techcommunity.microsoft.com/t5/exchange-team-blog/new-opt-in-endpoint-available-for-smtp-auth-clients-still/ba-p/2659652 - is not more valid as MS has disabled this.

have tried this also

but did not work.

ANy other solution will be highly appriciated 

REgards

Pankaj