Email (in and out) stopped working overnight
Over the last three days Thunderbird has virtually stopped working for me. I originally posted this description of my problem to the question “Cannot send email” which was active in April of this year, but in my case the problem seems to have become permanent and also includes the failure to deliver incoming email, so I thought it warranted the creation of a new question thread. Essentially the problem seems like the one noted above. After running for (literally) years my Thunderbird setup has suddenly over the last three days has (a) failed to deliver incoming e-mail after it arrives or when it is requested via “Get Messages”, & (b) failed to send output messages, claiming that the output server "was lost in the middle of the transaction". My internet provider is Primus Canada. In discussion with their technical support it appears that the handling of both incoming and outgoing emails by the servers is working as expected. In addition, webmail applications as run on Firefox, my i-pad, and my i-phone all seem fine (although inconvenient as a long-term working backup). The problem therefore seems to reside with Thunderbird, whose settings had not been changed at all for some time now. I am running Windows 10 Home 64 bit (v1909, build 18393.900), Thunderbird (68.9.0 - 32 bit), Firefox (77.0.1 - 64 bit) all of which are up-to-date versions. Has anyone any suggestions as to what may be happening, or further lines of investigation? [P.S. I should now add that Thunderbird does seem to perform a "batch" load of queued incoming e-mails, following a system shutdown/restart and reload of the program. In addition, the sending problem seems to have disappeared (at least temporarily and for messages sent to myself) after I simplified the Outgoing Mail Server definitions for smtp.primus.ca to a single default server used by all six of my e-mail accounts. I don’t know whether this was a fix or just coincidental.]
Все ответы (3)
Did your email supplier confirm they've not changed anything ( working as normal doesn't mean they haven't)? Things like port numbers, authentication methods etc. Try resetting them anyway. Try adding a free (gmail or "Outlook com") account. See if these work. If they do it's a clue.
What are your settings? They should be imap.primus.ca on port 993, SSL/TLS security, authentication = normal password, User Name = email address; outgoing smtp.primus.ca on port 465, SSL/TLS security, authentication = normal password, User Name = email address. Use those in TB, and if doesn't work, try the instructions they provide for the W10 Mail app.
What is your antivirus, and is the TB profile folder excluded fro AV scanning?
Thank you terrybernstein and sfhowes for your interest. My apologies for not taking up this issue again sooner, but the available time was taken up in trying to sort out what was a bigger problem for me (Word crashing, only solution eventually to uninstall/reinstall Microsoft 365 in its entirety). To return to the problem at hand -- I had checked the recommended settings which matched those given except for the server, which for historical reasons is pop.primus.ca on port 110 (as rechecked with primus support). In addition the characteristics of the problem (popping up for the first time years after many years service, resolving itself following a reboot, creeping back during the course of a session) didn't seem to jibe with an invalid setting -- on the whole, settings tend either to work or to fail on a constant basis. For this reason, I set out to try to isolate some other factor that was changing, and I have identified one which I will document here in order to keep you in the picture, but which I still need to confirm for certain. I have noticed that incoming emails that can be seen to be present in the server using Firefox or Safari do not get transferred to TB while my VPN is active, but are brought down en masse as soon as the VPN is disconnected (even without reloading TB). I will need to get in contact with Bitdefender and/or Primus to find out when and why this started happening, and what can be done about it (hopefully just an entry in a "good guy" table).