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

Lolu chungechunge lwabekwa kunqolobane. Uyacelwa ubuze umbuzo omusha uma udinga usizo.

Can not receive or send emails after updating to Thunderbird version 102.2.1

  • 6 uphendule
  • 2 zinale nkinga
  • 10 views
  • Igcine ukuphendulwa ngu mispragu

more options

I use Windows 10 Home (up to date) and my provider is Earthlink.net . Since updating to Thunderbird version 102.2.1 my emails are not arriving at my computer from the provider. Also, the links to Mozilla on the "about" information in Thunderbird are not working. Also, I tried sending an email to Mozilla via Thunderbird and the send button is grayed out. In essence, the current version 102.2.1 is not working for me other than retaining my messages prior to installing the update. I have never had a problem over the years of using Thunderbird. How do I fix this and/or when will a correction be forthcoming?

I use Windows 10 Home (up to date) and my provider is Earthlink.net . Since updating to Thunderbird version 102.2.1 my emails are not arriving at my computer from the provider. Also, the links to Mozilla on the "about" information in Thunderbird are not working. Also, I tried sending an email to Mozilla via Thunderbird and the send button is grayed out. In essence, the current version 102.2.1 is not working for me other than retaining my messages prior to installing the update. I have never had a problem over the years of using Thunderbird. How do I fix this and/or when will a correction be forthcoming?

All Replies (6)

more options

In addition to my initial message, there have been no error messages. My previous version was 91.13.0. I will try to reinstall that version from a reliable source. So far the only version that I have found for download is 102.2.1 .

more options

Try https://archive.mozilla.org/pub/thunderbird/candidates/102.2.2-candidates/build1/win64/en-US/Thunderbird%20Setup%20102.2.2.exe - take the defaults when installing so that it installs on top of your currrent thunderbird program directory. Is it better?

What exactly are you seeing with Help > About which makes you say it isn't working?

more options

I have posted this on another thread, too. FYI: Yes - I have this problem too. I upgraded to 102.2.2, and I had a fleeting certificate warning error - unfortunately I was distracted at the time and continued. But now: I receive no emails, and no sent emails are stored. I have a local Windows Server hosted TB, using IMAP, SSL/TLS PS - I have an 'inherited' IT system I don't know everything about - there was an existing certificate problem in that I could not email any Microsoft account - it would be rejected. Is there a tute you could direct me to, in case I can follow it and fix my local certificate issue? Failing that, is there an easy way to roll-back to the previous version TB? Thanks

more options

I am having a similar issue. Running 102.2.2. After it upgraded, I am no longer able to access my personal IMAP server. I'm running courier-imap on port 993 with a self-signed cert. Thunderbird says it's connected but it will not retrieve new messages nor allow me to save messages to Sent Mail folder.

I am not having this problem with other email clients nor an older version of Thunderbird on an xubuntu machine. I am able to connect to port 993 just fine and issue commands manually (using openssl via cygwin). I suspected cert problem and removed the 'exception' for this cert from the cert manager to see if it would prompt me but I have not see anything.

I am going to try to downgrade if possible to see if that works.

more options

Downgrading to 91.13.0 fixed the problem. I had to create a new profile since I was installing over a newer version. But I was prompted to confirm the self-signed cert and then it worked fine. I may try to install 102.2.2 but wipe out that account and add it again to see if that helps.

more options

No luck. Upgrading to 102.2.2 saw the same problem. Going to keep running 91.13.0 for now. :(