Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Weitere Informationen

why can't I send/receive email after Thunderbird installed a software update?

  • 3 Antworten
  • 4 haben dieses Problem
  • 15 Aufrufe
  • Letzte Antwort von jtmc

more options

Everything worked fine until this afternoon, when Thunderbird installed a software update. Now I can't send or receive email and I get a message that my email server has timed out. At the top of the message bar (next to "inbox") there is a spinning circle, like Thunderbird isn't connecting with the server? I've contacted my email provider (qnet.com) and they are working on it, but I thought I should check with you to see if there is something I can do....I have version 52.1.1. Thanks!

Everything worked fine until this afternoon, when Thunderbird installed a software update. Now I can't send or receive email and I get a message that my email server has timed out. At the top of the message bar (next to "inbox") there is a spinning circle, like Thunderbird isn't connecting with the server? I've contacted my email provider (qnet.com) and they are working on it, but I thought I should check with you to see if there is something I can do....I have version 52.1.1. Thanks!

Alle Antworten (3)

more options

common to these sorts of issues following an update are anti virus programs and their associated firewall. check that Thunderbird is being allowed and that the version number match.

more options

Thanks - how do I check my firewall? I have Windows Security Essentials, and I see that there are 2 Firefoxs allowed, but I don't know how to check what version they are or if they are Thunderbird....Ialso have Malewarebites, but I don't think that has anything to do with the problem....

Geändert am von jtmc

more options

For some reason, my email started working again! I suspect that qnet.com did something on their end..... Thanks for the help!!