"Connection to server mail.twc.com was reset"
Hello. I am a non-technical guy who would appreciate any help on this.
We have 3 laptops in our home, 2 running Thunderbird and 1 running Windows Live Mail. The latest TB version is installed: 78.3.2. Our ISP is Spectrum. The last several months everything has been running fine but beginning yesterday (10/7/20), on the TB computers we started getting the message "Connection to server mail.twc.com was reset". On the WLM computer the message was "Unable to send or receive messages for the pop-server.austin.rr.com account" (etc.) and we (mostly) can't send or receive emails. I say mostly because once or twice since the problem began yesterday, we would get a dump of several emails, then it would go right back to the error message.
Our internet connection is fine and we are fully functional on the web. We have not fiddled with any of our email settings (ports, etc.). And I can access our emails through Spectrum's webmail (although I dislike using it and much prefer TB).
I have read of a few possible fixes as to TB and tried one: changing the TLS Security Version minimum from 1.3 back to 1.1. It didn't help so I switched it back to 1.3, the current default.
I think I saw that TB 78.3.2 was automatically installed a couple of days ago, so thought maybe that was it. But then I didn't see how Windows Live Mail was having a very similar problem just as suddenly. I really don't want to revert to an older version of TB both because I would lose any security and other improvements and because I don't know if I'm even competent to do the operation (I'm very non-technical).
I called Spectrum Tech. Support, and they were even less help than usual, insisting that since I could send and receive email via their webmail, it was a syncing problem and they couldn't help.
I would really appreciate any advice or suggestions. Thanks, Andrew
所有回复 (1)
10/11/20 update: The problem seems to have resolved itself, on all 3 of our laptops, without my doing anything. This would seem to suggest that the problem was with the Spectrum servers, which I suspected but which they will never admit.