Ce site disposera de fonctionnalités limitées pendant que nous effectuons des opérations de maintenance en vue de vous proposer un meilleur service. Si un article ne règle pas votre problème et que vous souhaitez poser une question, notre communauté d’assistance est prête à vous répondre via @FirefoxSupport sur Twitter, et /r/firefox sur Reddit.

Avatar for Username

Rechercher dans l’assistance

Évitez les escroqueries à l’assistance. Nous ne vous demanderons jamais d’appeler ou d’envoyer un SMS à un numéro de téléphone ou de partager des informations personnelles. Veuillez signaler toute activité suspecte en utilisant l’option « Signaler un abus ».

En savoir plus

Ce sujet de discussion a été archivé. Veuillez poser une nouvelle question si vous avez besoin d’aide.

Not receiving e-mails after upgrade to 52.1.1

  • 3 réponses
  • 1 a ce problème
  • 12 vues
  • Dernière réponse par user1121639

rudolfl1971
rudolfl1971
more options

Hi all,

Today Thunderbird upgraded itself to 52.1.1 (W10, 32-bit) and stopped working. E-mails are not received. All I see is message in status bar "Checking mail server capabilities".

Server is IMAP. Server is definitely working as I receive e-mails on my mobile and on Thunderbird on my Mac.

Was working happily before upgrade.

Any ideas?

Thanks, Rudolf

Hi all, Today Thunderbird upgraded itself to 52.1.1 (W10, 32-bit) and stopped working. E-mails are not received. All I see is message in status bar "Checking mail server capabilities". Server is IMAP. Server is definitely working as I receive e-mails on my mobile and on Thunderbird on my Mac. Was working happily before upgrade. Any ideas? Thanks, Rudolf

Solution choisie

First, Download & install the latest version of Thunderbird, which is 52.2.0.

Then if there is still a problem, check to make sure that your antivirus/firewall program is not blocking Thunderbird.

The #1 reason for Thunderbird to not be able to send or receive e-mail right after the program has updated, is that the antivirus/firewall software installed doesn't recognize the new Thunderbird version, so blocks it.

The situation usually resolves itself when the antivirus/firewall software updates in a day or two.

Or you can go into the settings of the security software to tell it to allow Thunderbird.

Please reply here after doing these two things. If there is still a problem, we can go from there.

Lire cette réponse dans son contexte 👍 0

Toutes les réponses (3)

user1121639
user1121639
more options

Solution choisie

First, Download & install the latest version of Thunderbird, which is 52.2.0.

Then if there is still a problem, check to make sure that your antivirus/firewall program is not blocking Thunderbird.

The #1 reason for Thunderbird to not be able to send or receive e-mail right after the program has updated, is that the antivirus/firewall software installed doesn't recognize the new Thunderbird version, so blocks it.

The situation usually resolves itself when the antivirus/firewall software updates in a day or two.

Or you can go into the settings of the security software to tell it to allow Thunderbird.

Please reply here after doing these two things. If there is still a problem, we can go from there.

rudolfl1971
rudolfl1971 Auteur de la question
more options

Thank you,

I resolved the problem over weekend and it was not Thunderbird related. Rather an coincidence.

To temporary "fix" the issue, I set up Thunderbird to use insecure connection and send password plain. It would always fail when SSL was in use.

At about time I upgraded Thunderbird, mail server had its SSL certificate screwed up. Took me a while with cPanel support to figure out the problem and re-issue new certificate.

The problem with Thunderbird, however, is the fact it did not tell me about it. Thunderbird was just sitting there, showing "Checking mail server capabilities" forever. It should show some sort of error popup saying certificate of server is no longer valid.

Thanks, Rudolf

user1121639
user1121639
more options

It might be useful to point out this issue with Thunderbird by submitting a bug.