Exception: The remote certificate is invalid according to the validation procedure
Problem reported by Steve Norton - September 1 at 6:22 AM
Submitted
I upgraded from 16.3.6705 to 16.3.6816 and outbound connections to 188.125.73.28:465 fail with Exception: The remote certificate is invalid according to the validation procedure
[2018.09.01]    at System.Net.Security.SslState.StartSendAuthResetSignal(ProtocolToken message, AsyncProtocolRequest asyncRequest, Exception exception)
[2018.09.01]    at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
[2018.09.01]    at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
[2018.09.01]    at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
[2018.09.01]    at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
[2018.09.01]    at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
[2018.09.01]    at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
[2018.09.01]    at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
[2018.09.01]    at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
[2018.09.01]    at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
[2018.09.01]    at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
[2018.09.01]    at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
[2018.09.01]    at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
[2018.09.01]    at RelayServer.Clients.SMTP.ClientConnectionSync.InitiateSsl(Boolean validateAllCerts)
[2018.09.01]    at RelayServer.Clients.SMTP.SmtpClientSession.Initialize(String #qCb, List`1 #RVi, String #64i)
I've verified the certificate and it's chain within the OS and there are no issues. The certificate has been in place for most of the year and I've not had a problem like this. I've reverted to 16.3.6705 and mail is being sent correctly again.

5 Replies

Reply to Thread
1
Paul Blank Replied
Hope this is not an issue with V15 as well. 
0
echoDreamz Replied
Have you tried using a valid hostname that matches the certificate to connect instead of the IP?

Christopher

0
raneri andrea Replied
Hello Steve, is your problem with smartermail: 
Exception: The remote certificate is invalid according to the validation procedure 
resolved ?
I'have same problem from 05/09/18 after update, but I see this only now
Thanks
Andrea Raneri
0
Steve Norton Replied
@echoDreamz - I'm already using a hostname that matches the certificate and that then resolves to 188.125.73.28.
@raneri andrea - It is with SmarterMail, I've not tried any versions since so I don't know if the problem has been resolved.
0
Steve Norton Replied
I've upgraded to SmarterMail 16.3.6885 and mail is now correctly sent but I do get " Certificate name mismatch." in the logs which is not true according to https://www.sslchecker.com/sslchecker which has smtp.tools.sky.com as a hostname match on the certificate.

Reply to Thread