Using Classic Outlook on Windows for personal email, calendar, and contact management
Thank you Chloe for taking the time to reply. I very much appreciate it!
1. Verify Comcast POP settings
Done. "587 + STARTTLS" does not work at all when "Test Settings" is executed while "465 and SSL" can successfully send and receive a test message if Outlook is behaving.
2. Manage credentials in Outlook
Credential Manager and I have become good friends through this process (well before your suggestion). Deleting "Windows Credentials" --> "Generic Credentials" containing "SSO_POP_ ..." and any that have a timestamp of "Today" and "Persistence" of "Login" can provide some relief but it can take a few tries for it to sink in and work. This, more than anything, tells me that it is a Microsoft bug with these credentials and how they use them in relation to the fully-functional password that has been saved by me within Outlook, and that still continues to function with Comcast without change when it suits the whims of Outlook.
3. Issues after sleep / restart
- "You must switch back to Outlook Classic to access the full POP advanced settings tabs" --- I am already using Outlook classic so that all the POP3 settings are available to me.
- "disable 'Leave a copy of messages on the server' (if your workflow allows)." -- Sorry, my workflow does not allow. They must remain on the server for 7 days or until locally deleted so that both my desktop and laptop have a shot at pulling them down.
- In Device Manager > Network adapter > Properties > Power Management, uncheck “Allow the computer to turn off this device to save power.” -- Done, time will tell if it matters.
4. Test outside of Outlook
- Try with another mail client (e.g., Thunderbird, or run: openssl s_client -connect mail.comcast.net:995 ) to confirm that Comcast is not intermittently blocking POP. If another client works fine, the problem lies with Outlook. -- Not yet tried but not likely the problem since a reboot or sign out/in temporarily restores it to a functional state and the odds of Comcast always lifting their block after one of those events is not reasonable.
5. Outlook 365 POP bug
Since mid-2025, there have been reports of Outlook 365 breaking POP with Comcast/Yahoo. You are on build 16.0.19231.20138, so try:
- Update Office manually: File > Office Account > Update Options > Update Now. -- It was already up to date as of yesterday. I'll check again when I return home this evening.
- If updating does not help, roll back to an earlier Office build (Microsoft provides rollback steps via OfficeC2RClient.exe). Some patches have widely broken POP. -- Microsoft broke something with a patch? Surely you jest! I wonder how far I can roll things back? In the extreme, I still do have my Office 2003 DVD and product keys. I'll bet that will fix it (at the expense of MS's 365 future revenue stream).
6. Comcast-specific issues
- Comcast may “silently block” POP after multiple failed login attempts, causing POP to stall. Log into Comcast webmail > My Account > Security > Manage Xfinity ID to check for any security alerts. -- No Xfinity security alerts are showing and while what you suggest is possible, it is not likely because the Outlook failures to connect start immediately after resumption from sleep; there are no multiple attempts leading up to it.
- Sometimes you must reset your Comcast password, even if webmail still works, because the backend POP authentication may reject the old password. -- Again, not likely because my saved Xfinity credentials (saved by me within Outlook) continue to function with Comcast without change when it suits the whims of Outlook. If the password were deemed bad by Comcast, they would not start accepting it again 5 minutes later after a sign out/in.
Please feel free to let me know if you have any further updates, thanks.