Updated Thunderbird will not send or receive emails.
Thunderbird 115.2.0 was installed on my computer yesterday. Now I can't send or receive email messages. When I try to download my messages, the line at the bottom of the screen says, "Host contacted, sending login information..." This stays visible for quite some time, then finally goes blank. No messages are downloaded. When I try to send a message, the program tries for quite a while, then says, Sending of the message failed. The message could not be sent because the connection to Outgoing server (SMTP) smtp.gmail.com timed out. Try again. Needless to say, I have tried again and again, but nothing changes. This has got to be because of the update. None of my settings are any different from what they were two days ago when everything worked. As noted above, my server is gmail. Please help.
由CarolynHoglin于修改
被采纳的解决方案
Every morning I open Thunderbird and try to get my new messages. Every morning nothing happens and I have to go to webmail.
That is, until this morning. Without my doing anything about this situation since I started this thread, suddenly my Gmail messages are coming through. I am also able to send messages.
As I said before, the problem was in the update, and Thunderbird has now fixed it.
定位到答案原位置 👍 1所有回复 (5)
Same here! It's very annoying.I'm getting the timed out message, but mine is smtp.atlanticbb.net
Same issue here, but mine is timed out connection smtp.atlanticbb.net
I have discovered that Thunderbird will work with vfemail.net, but not with gmail.com.
Does anyone know how to fix this problem?
There are generally not problems with gmail.
Have you seen https://support.mozilla.org/en-US/kb/cannot-send-messages ?
选择的解决方案
Every morning I open Thunderbird and try to get my new messages. Every morning nothing happens and I have to go to webmail.
That is, until this morning. Without my doing anything about this situation since I started this thread, suddenly my Gmail messages are coming through. I am also able to send messages.
As I said before, the problem was in the update, and Thunderbird has now fixed it.