Error: Timeout when setting up SSL/TLS
-
Sebastien Varrette
Complementary, it seems that our organisation went to NTLM authentication, that could be the source of the problem.
Does that help you to have an idea of the issue ? -
Sebastien Varrette
Apparemment, ce n'est pas ce qui est forcé, mais bien le starttls i.e. TLSv1 (au lieux de SSL v3)
J'ai l'impression que CFnetwork ne supporte pas cela (cf le logconnect to <smtp.domain.com> on port 587 (CFNetwork) without STARTTLS (required).
Serait il possible de tester dans la configuration pour forcer TLS ? La configuration actuelle 'Use SSL' ne laisse pas cette possibilité. -
Sebastien Varrette
Note: following ticket #1585, I suffixed the port for SMTP with
p(thus changing from587to587p) and this seems to enforce startTLS now.
However the sending action now failed with the message 'Unspecified Error' in the popup.09:26:27 Handling reply 09:26:27 Sending request (1161) 09:26:27 Handling request 09:26:27 Clearing connection to <smtp.domain.com> 09:26:30 Ready to run action (retry count: 3) 09:26:30 Clearing connection to <smtp.domain.com> 09:26:30 Trying to connect to <smtp.domain.com> on port 587p (CFNetwork) with STARTTLS (required) 09:26:30 Resolved hostname (<smtp.domain.com>). 09:26:30 Successful connection. 09:26:40 Error code: 2 09:26:40 Failed action (0). Reset observed read/write timeouts: 8/8 -
benny
It appears it fails before NTLM authentication (which MailMate cannot do which means that might also be a problem, but first we need to connect). Could you provide the real SMTP hostname. That would allow me to reproduce the issue. You can use “Help ▸ Send Feedback” if you have a working account in MailMate and you don't want to share the hostname.
-
Sebastien Varrette
So our IT service seems to have reverting some setting at the network level -- that might explain the CFNetwork error code 2 cfHostErrorUnknown:
An unknown error occurred (a name server failure, for example).Now things are working fine, however it might indicate that may be Mailmate should allow for a more deeper analysis of the subsequent certificates used; or a link to the CFNetwork error explaination ?
Anyway, thanks for your feedback, things are fine now.
-
benny
- State changed from new to resolved
The error code is an internal error for timing out on a request. It's not a CFNetwork error.
-
Sebastien Varrette
This issue reappeared upon reboot ;(
-
benny
@Sebastien: I've replied to your email.
-
benny
- State changed from resolved to cantreproduce
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.