03-23-2018 08:50 AM - edited 03-08-2019 07:35 PM
Solved! Go to Solution.
03-27-2018 07:17 PM
Hey Doug,
I had a look at your TAC case as well; I suspect that error is with relation to the SSL client helo negotiation.
Using a packet capture would help yield for further information.
(Otherwise giving the TAC engineer remote access (tunnel) they can run other verification.
Thanks,
Matthew
03-24-2018 07:52 PM
03-26-2018 07:49 AM
03-26-2018 03:16 PM
Hey Doug,
This is quite interesting :
This error is indicative that your ESA attempted to send the email many times and failed; obviously as your side had TLS set to required.
For me the best course of action if the issue does recur is to run a telnet test to this destination server and see if TLS is offered or run a tlsverify action just to check the TLS negotiation - when it shows TLS unavailable, it didn't even get to the cipher negotiations; it looks like it was possibly unable to get a response from STARTTLS.
Regards,
Matthew
03-27-2018 09:47 AM - edited 03-27-2018 09:52 AM
03-27-2018 10:10 AM
03-27-2018 02:22 PM
03-27-2018 07:17 PM
Hey Doug,
I had a look at your TAC case as well; I suspect that error is with relation to the SSL client helo negotiation.
Using a packet capture would help yield for further information.
(Otherwise giving the TAC engineer remote access (tunnel) they can run other verification.
Thanks,
Matthew
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide