Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More
Archived

What's with the newest update not connecting to SMTP server about half the time?

GEOFFJL replied
GEOFFJL

When it's doing this, re-entering my password as requested doesn't help, but that's not a surprise, because it didn't magically become wrong in the first place. Sometimes retrying right away succeeds...sometimes I have to wait awhile and keep trying. I doubt it's the fault of the server, because the problem started immediately after I assented to the most recent Thunderbird update. I've previously trusted the updates, but maybe now I'd better be more cautious: my work-day frequently requires that I send something to a customer and immediately move on to what's next.

When it's doing this, re-entering my password as requested doesn't help, but that's not a surprise, because it didn't magically become wrong in the first place. Sometimes retrying right away succeeds...sometimes I have to wait awhile and keep trying. I doubt it's the fault of the server, because the problem started immediately after I assented to the most recent Thunderbird update. I've previously trusted the updates, but maybe now I'd better be more cautious: my work-day frequently requires that I send something to a customer and immediately move on to what's next.

All Replies (4)

using McAfee? That is exactly how it makes Thunderbird work. Although all Anti virus programs do similar things at times.

Turn off email scanning of your outgoing mail and see if that helps. I really don't understand it's purpose, the product doing the scanning has assured you you have nothing contagious and these things don't just appear out of thin air. anyway.

Nope, not using McAfee. In fact, since I'm on a Mac, I wasn't even using ANY security suite for awhile. Then I got a deal on Kaspersky, so I tried it. Everything was fine for several weeks…then Thunderbird updated and hell broke loose. In addition, a friend who I got to use Thunderbird many years ago complained about the same thing to me after I made my earlier post…said it's been happening for about a week - starting when SHE updated, too. She's on a PC using Avira security - not McAfee, not Kaspersky.

If in fact the anti-virus has something to do with the problem, Mozilla ought to undo whatever change they did, because it makes no sense to do something that will only work right on a system with no internet security installed. (I'm currently trying to pry out of Kaspersky how to JUST disable email scanning, since what they claim exists doesn't in my version.)

But in addition, in case it matters, my Mac registers a system-level error in its log whenever this happens, which I don't think would be the case if it were due to an antivirus program doing exactly what it's supposed to.

do you think it might be germain to share the system level error details? Error codes messages etc?

We know what you tell us and really it is more than difficult if we are guessing.

Original Thunderbird error message is always: "Login Failed - Login to server smtp.att.yahoo.com failed…Enter New Password…Cancel…Retry"

SMTP configuration: port 465, authentication normal password, connection security SSL/TLS. These settings are what my provider specifies, and they have worked for years. They even work now when the stars are aligned correctly.

System error:

Jun 18 12:06:29 SLOWDOWN: client 0x7fc850819600 (pid 11) sleeping due to too many errors (num usleeps 1115)

There are literally dozens of these, many with time-stamp corresponding to efforts to send, when I just *couldn't* wait and had to insist multiple times before sending finally went through. I don't remember times for ALL the instances, in many of which I gave up, stored a draft, and came back to it later.

I spent this morning with "protection off" on my anti-virus, and the problem continued unabated. I saw no evidence of any usual AV functions proceeding as usual, so I believe switching off worked.

With all the complaints that have recently been building up online, is Mozilla still denying this has anything to do with Thunderbird?

Do you know of any way to obtain a prior version install file and revert?