This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

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

Cannot get mail (Thunderbird 78.5.1, Windows 10 Pro 1909, no ESET products installed)

  • 11 replies
  • 1 has this problem
  • 6 views
  • Last reply by laurasha

more options

Yesterday, when trying to send an email, I got a message saying there was an issue with the certificate from my ISP (this was a known bug that they were working on). I accepted the certificate so I could send the email.

Since then, Thunderbird hasn't been able to receive any emails. I can get emails from my ISP through their webmail interface and on my phone. None of my Thunderbird account settings have changed as far as I can tell. I am not highly experienced with Thunderbird.

Incoming server account info: IMAP, port 993, SSL/TLS, Normal password

I did see the messages here about the ESET issue and confirmed I have no ESET products installed. Suggestions?

Yesterday, when trying to send an email, I got a message saying there was an issue with the certificate from my ISP (this was a known bug that they were working on). I accepted the certificate so I could send the email. Since then, Thunderbird hasn't been able to receive any emails. I can get emails from my ISP through their webmail interface and on my phone. None of my Thunderbird account settings have changed as far as I can tell. I am not highly experienced with Thunderbird. Incoming server account info: IMAP, port 993, SSL/TLS, Normal password I did see the messages here about the ESET issue and confirmed I have no ESET products installed. Suggestions?

All Replies (11)

more options

What is the antivirus? Some, like Avast/AVG, block connections if their 'Mail Shield' or equivalent is active, or scanning of secure SSL connections is on.

more options

I'm using Malwarebytes. It hasn't upgraded since yesterday, and anyway it doesn't seem to have any settings that are specifically about mail. It does have settings related to Outlook but obviously I'm not using that.

more options

It looks like the ISP hasn't corrected the problem yet. Under Options/Privacy & Security/Certificates, Manage Certificates, certificates can be inspected and removed. Can you find the one for your ISP?

more options

I see one for my ISP (which reports that all problems are resolved). Should I remove it?

more options

Actually, it appears I have two for my ISP, one dated yesterday and one dated 12/5/2021. They use different ports as well. Should I delete one of them? If so, which?

more options

I would remove the older one, after backing up the cert9.db file in the profile folder: Help/Troubleshooting, Profile Folder, Open Folder, close TB, rename cert9.db to cert9.db.bak. The port on the cert. should match the port specified in incoming or outgoing server settings in Tools/Account Settings, e.g. 993 or 465/587.

more options

Thanks, @sfhowes. I followed your instructions (very clear, BTW, thanks), but unfortunately it didn't fix the problem. I still can't get mail. The blue donut just spins and spins next to where it says "Inbox".

more options

It appears I also cannot send mail. I get error messages about certificates. I confirmed that the certificates match the specified ports for my incoming and outgoing mail servers.

more options

I was able to get help from the ISP. Okay to close this ticket.

more options

For the benefit of others reading this topic, can you say what the ISP did that fixed it?

more options

They had me change the server names. They had, since time immemorial, been my domain names (mail.domain.com), but the ISP apparently prefers smtp.ispname.com etc. Which is wacky, because it's worked the other way all this time. I don't know if this will be useful to anyone else, but that solved it.