cannot make connection to mail server, smtp fine. settings match reccommended and not getting password popup after removing old ones.
I have not been able to make a connection to the mail.comcast.net for a day now. I see the connecting bar at the bottom but get a failure that it failed to connect. I cleared the password manager. but no popup appears to enter my password in. So without authentication, it cannot get the email. I can't force the login popup to appear to enter the new password.
Server settings are fine, I am using POP3 which is remaining a valid choice. I use avast, current version (autoupdate) Thunderbird is current too. My firewall is WindowsDef, but Thunderbird is on allowed list. I have briefly turned off both Avast and still no connection. I', not sure if defender is blocking even if I selected it. Comcast of course denies anything as the web interface is fine ATM.
(this is not the router or modem as another laptop using thunderbird (probably older as it's my mother's) opens fine. I have done little else for the last day and have run out of things the check, help>! Thanks
被采纳的解决方案
It took almost 48 hours, but email is working again. I didn't think it was thunderbird, though it was the only app that was not connecting to other sites as far as I could see.
I'm not sure which action fixed it as I kept checking email like a mining canary, so I will list the last few steps:
- removed old A/V Avast free
- started installing AVG free
- --!!-- AVG complained that the BFE service was disabled. enabled and started
- finished install, scanned, and AVG seemed happy
- windows could not detect proxy settings. Dunno when this started, but it started X months ago without any visible issues. But after several different places, the green touchstyle interface changed the proxy settlings and took.
Opened Thunderbird>failed to connect. in small disgust, watched the last few minutes of a TV show and checked email on web interface... needed an email address from Thunderbird for my writing partner. Opened Thunderbird> ASKED FOR PASSWORD opened and downloaded dozens of email... The proxy settings seems likely but I used it for months before I noticed or even remembered the complaint. The BFE being off was odd too. Whichever of these was the deciding issue, plainly the fix took some time to propigate. Hope this helps someone else someday...
定位到答案原位置 👍 0所有回复 (4)
My POP settings were already mail.comcast.net on port 995 SSL and password. (though a comcast tech had suggested 993 without resullt)
Restarted in Safe mode, and I still got the server failure to connect to mail.comcast.net. thanks!
re :I cleared the password manager. but no popup appears to enter my password in. So without authentication, it cannot get the email. I can't force the login popup to appear to enter the new password.
Assuming you still cannot enter password.... What version of Thunderbird are you using?
version 52.9.1 (up to date)
选择的解决方案
It took almost 48 hours, but email is working again. I didn't think it was thunderbird, though it was the only app that was not connecting to other sites as far as I could see.
I'm not sure which action fixed it as I kept checking email like a mining canary, so I will list the last few steps:
- removed old A/V Avast free
- started installing AVG free
- --!!-- AVG complained that the BFE service was disabled. enabled and started
- finished install, scanned, and AVG seemed happy
- windows could not detect proxy settings. Dunno when this started, but it started X months ago without any visible issues. But after several different places, the green touchstyle interface changed the proxy settlings and took.
Opened Thunderbird>failed to connect. in small disgust, watched the last few minutes of a TV show and checked email on web interface... needed an email address from Thunderbird for my writing partner. Opened Thunderbird> ASKED FOR PASSWORD opened and downloaded dozens of email... The proxy settings seems likely but I used it for months before I noticed or even remembered the complaint. The BFE being off was odd too. Whichever of these was the deciding issue, plainly the fix took some time to propigate. Hope this helps someone else someday...