1235616 - Falsely timing out on port 465 SMTP server

Status: RESOLVED WORKSFORME

(MailNews Core :: Networking: SMTP, defect)

Description

[Brian Byrd]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_2) AppleWebKit/601.3.9 (KHTML, like Gecko) Version/9.0.2 Safari/601.3.9

Steps to reproduce:

Send an e-mail via my hosting SMTP server on port 465 with SSL.


Actual results:

Immediately, without any delay, I get this error message dialog:

"Sending of the message failed.
The message could not be sent because the connection to Outgoing server (SMTP) secure183.inmotionhosting.com timed out. Try again."

When I try again, the message sends fine, and subsequent messages continue to send fine for as long as I'm running TB. Once I quit TB, and launch it again, I get this same error message the first time, and only the first time, I try to send mail.

Seems like there is some sort of initialization error when TB tries to make the first connection to this SMTP server that somehow gets resolved before the second try.

When using another e-mail client, like OS X Mail for example, this problem does not occur. Nor does it occur under iOS. It is happening for me only with TB, on both a Mac and a Windows machine here at home.

The week before I started having this problem I was using 1&1 as my mail host, was connecting with a secure connection (but not SSL on port 465), and was not having this problem. It started once I switched to InMotion Hosting and their specific SMTP connection.

When I contacted InMotion Hosting about this problem, they wrote: "We have been hearing reports of the same issue you are experiencing with Thunderbird 38.4.0 over SSL connection."


Expected results:

Mail should send properly each time, and not give this error message when trying to send mail the first time after launching TB.

Comment 1

[Wayne Mery (:wsmwk)]

Brian are you still seeing ths problem?

Comment 2

[Brian Byrd]

Thanks for checking in with me. No, the problem has disappeared. Either my ISP made a change on their end, or somehow the issue got fixed in TB. Either way, I've been happy for a few months now.

Since I'm new to the Bugzilla process, do I need to change the status to Resolved, or can you do that, or what? Please let me know if I need to do anything else. Thanks!