Intermittent send message error: Outgoing server (SMTP) smtpout.secureserver.net timed out
We have a number of GoDaddy Workspace email accounts which we have set up in Thunderbird for multiple users on a Windows Server 2012 computer. Over the last few months we've been getting an intermittent but ongoing error when sending. As soon as the user clicks 'Send' a message box titled "Send Message Error" comes up saying:
"Sending of the message failed. The message could not be send because the connection to Outgoing server (SMTP) smtpout.secureserver.net timed out. Try again."
Clicking 'OK' closes the message and the user can try clicking 'Send' again. Upon repeated attempts the message will eventually be successfully sent.
Configuration: Thunderbird 38.7.1 Account Type: POP3 Server Name: smtpout.secureserver.net Port: 465 User Name: (full email address) Authentication method: Normal password Connection Security: SSL/TLS
This happens will multiple account on this computer in Thunderbird but doesn't seem to happen when sending from smartphones.
Things I've tried: - Changing 'Connection Type' to none and using port 80 or 3535. - Using about:config to increase mailnews.tcptimeout to 2000. - Running compact and repair on the various Thunderbird folders (Inbox, Drafts, Outbox, Sent). - Disabling Trend Micro firewall and adding thunderbird.exe to Trusted Programs List.
I spoke with GoDaddy support but the tech basically said that Thunderbird is really supported by GoDaddy and recommended another client. That isn't the solution I'm looking for.
I have good technically knowledge so I'm happy to try various tests to narrow down the cause.
Thanks for any help you can offer!
All Replies (1)
Marc, our experience here as been very similar. There doesn't seem to be a particular pattern to why the message will send after repeated attempts.
I've had our users run Thunderbird through a batch file which dumps the SMTP logs to a file using the following criteria: set NSPR_LOG_MODULES=smtp:5,timestamp
It seems like when the "server timeout" error shows up for the user, the following lines are logged. Sadly the log doesn't provide any further detail, or even any specific error message:
- 2016-04-25 20:46:53.622000 UTC - 21488[1411140]: SMTP Connecting to: smtpout.secureserver.net
- 2016-04-25 20:46:57.095000 UTC - 21488[1411140]: SMTP Connecting to: smtpout.secureserver.net
- 2016-04-25 20:47:00.029000 UTC - 21488[1411140]: SMTP Connecting to: smtpout.secureserver.net
- 2016-04-25 20:47:04.784000 UTC - 21488[1411140]: SMTP Connecting to: smtpout.secureserver.net
For successful sends, the log looks like this:
- 2016-04-22 18:28:42.162000 UTC - 0[2e11140]: SMTP Connecting to: smtpout.secureserver.net
- 2016-04-22 18:28:42.563000 UTC - 0[2e11140]: SMTP entering state: 0
- 2016-04-22 18:28:42.563000 UTC - 0[2e11140]: SMTP Response: 220 p3plsmtpa11-04.prod.phx3.secureserver.net ESMTP
- 2016-04-22 18:28:42.563000 UTC - 0[2e11140]: SMTP entering state: 14
- 2016-04-22 18:28:42.563000 UTC - 0[2e11140]: SMTP Send: EHLO [xxx.xxx.xxx]
- And carries on from there.
One thing that does seem strange to me is that at the conclusion of logging a successful send and before the next "SMTP Connecting to" line there is always the line like:
- 2016-04-22 18:26:09.593000 UTC - 0[2e11140]: SMTP connection error quitting 804b0002, ignoring
Anyway, I don't feel like the logs have been very helpful but perhaps someone else will be able to glean some direction from them.