SMTP "timed out"
Categories
(MailNews Core :: Networking: SMTP, defect)
Tracking
(Not tracked)
People
(Reporter: jacqui, Unassigned)
References
Details
(Keywords: regression, testcase-wanted)
Attachments
(1 file)
9.34 KB,
image/png
|
Details |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36
Steps to reproduce:
When sending an email, I received the attached message.
"Sending of the message failed. The message could not be sent because the connection to Outgoing server (SMTP) secure.emailsrvr.com timed out. Try again."
Actual results:
I tried re-sending the email a couple times and received the same message. Eventually, the message sent successfully. The problem is occurring inconsistently. Sometimes, messages send without issue, and other times this occurs.
Expected results:
I have not had any issues with this up until the last week or two. I have been using Thunderbird for at least a year, and I set up my server settings a long time ago. I have not changed anything.
Comment 1•1 year ago
|
||
You can try changing a timeout value in the Thunderbird Config Editor.
Main menu > Settings > Config Editor
Be warned that changing any settings in the Config Editor can cause problems. If you change a setting, you should make a careful note of what you change so that you can change it back to how it was before you started changing it. When you are done testing, you should undo any changes that you made.
There are about a hundred different timeout settings. I don't know which one would be applicable here. In my settings, if I search for "timeout" I find a setting whose name begins with "mail.server". This might be applicable.
I hope this helps.
Comment 2•1 year ago
|
||
At this point, there are no further updates coming to version 102.
If this reproduces for you with version 115, let us know so we can reopen the bug.
Comment 3•1 year ago
|
||
I'm able to reproduce this problem with Thunderbird 115.3.1. Attempting to send a message via SMTP results in an immediate "timed out" error. Immediately trying to resend works. The problem started happening only four days ago, after an update from 115.3.0 to 115.3.1. It's only this Thunderbird installation that's having the problem; my other machines (some of which are also running Thunderbird 115.3.1) have no problems connecting to the same mail server.
Comment 4•1 year ago
|
||
(In reply to Tristan Miller from comment #3)
The problem started happening only four days ago, after an update from 115.3.0 to 115.3.1. It's only this Thunderbird installation that's having the problem; my other machines (some of which are also running Thunderbird 115.3.1) have no problems connecting to the same mail server.
None of the code change in 115.3.1 should be impacting sending or receiving of messages. I bet if you go back to 115.3.0 the problem will continue.
Does Bug 1810216 describe your issue? (109.x Send Message via SMTP failed due to embedded images)
Comment 5•1 year ago
|
||
(In reply to Wayne Mery (:wsmwk) from comment #4)
None of the code change in 115.3.1 should be impacting sending or receiving of messages. I bet if you go back to 115.3.0 the problem will continue.
Does Bug 1810216 describe your issue? (109.x Send Message via SMTP failed due to embedded images)
No, Bug 1810216 doesn't seem to match. I'm always sending plain-text messages, usually without any attachments.
Updated•1 year ago
|
Updated•1 year ago
|
Comment 6•10 months ago
|
||
Perhaps fixed by bug 1854567 in 115.6.0, available next week.
Please post your results of using that version.
Comment 7•10 months ago
|
||
I don't currently have access to the machine with which I encountered this bug. I'll get access to it again in a few weeks, at which time I'll test with Thunderbird >= 115.6.0.
Comment 8•9 months ago
|
||
I now have access to the machine with which I was experiencing this behaviour. It's now running Thunderbird 115.6.1 and I haven't been able to reproduce the problem.
Updated•8 months ago
|
Comment 9•8 months ago
|
||
Thanks Tristan
This bug doesn't have a patch, so duping to the fixed bug
Description
•