Outlook 365 repeatedly fails send/receive to POP server with prompts for password

WNM-1677 5 Reputation points
2025-09-30T00:36:16.2266667+00:00

Comcast currently acts as a POP server for Outlook 365 Classic running under Windows 11 on three different computers, two of which use one Comcast email account and the other uses a different email account. Recently (within the past month) the ability of Outlook to download email from the POP server to an of the computers for either email account fails about 90% of the time. When a send/receive is requested, the Send/Receive progress window shows that sending completes but receiving hangs until the window times out and a prompt to reenter the server password appears. Whether or not the server password is reentered makes no difference nor does it matter whether the "save password" box is checked. The only thing that seems to help is to reboot the computer and then it will work for a while, using the information that Outlook already has for the POP account. A computer "sleep" period is usually enough to render Outlook non-functional.

Microsoft® Outlook® for Microsoft 365 MSO (Version 2509 Build 16.0.19231.20138) 64-bit

For the Comcast POP server accounts, both sending & receiving require name/PW authentication. Incoming port is 995, using SSL encryption. Outgoing port is 465 with SSL/TLS encryption. No 2-factor authentication is used.  Comcast email access using their web interface works fine.  I am absolutely NOT interested in switching from POP access to IMAP as that would break the spam filtering application that is in use here, along with the fact that I want my emails stored locally rather than on any company’s server.

"Outlook.Com" is not used (or at least not to my knowledge; it better not be) for any of these accounts. 

What can be done to return Outlook to proper functionality?

Outlook | Windows | Classic Outlook for Windows | For home
0 comments No comments

2 answers

Sort by: Most helpful
  1. WNM-1677 5 Reputation points
    2025-09-30T15:16:29.9866667+00:00

    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.

    Was this answer helpful?


  2. Chloe-V 15,330 Reputation points Microsoft External Staff Moderator
    2025-09-30T07:48:24.7733333+00:00

    Hi WNM,

    Thank you for posting to Microsoft Q&A Forum.

    Based on your description, the issue is not really caused by the password itself, but more likely due to instability between Outlook 365 and Comcast’s POP server that has appeared in the past few months. Below are the troubleshooting steps in order:

    1. Verify Comcast POP settings

    Although you are listed them, Comcast has recently tightened authentication requirements. Double-check:

    • Incoming (POP3): mail.comcast.net, Port 995, SSL/TLS enabled.
    • Outgoing (SMTP): smtp.comcast.net, Port 465 (SSL) or 587 (STARTTLS).
    • Authentication: Must be enabled for both sending and receiving.
    • Username: Full Comcast email address (including @comcast.net).

    If you are using port 465 and still experiencing issues, try 587 + STARTTLS — Comcast specifically recommends this setting in some cases.

    2. Manage credentials in Outlook

    The repeated password prompts (even when the password is correct) are often caused by a corrupted Windows Credential Manager cache:

    1. Close Outlook.
    2. Open Windows Credential Manager:
    • Press Windows + R > type: control /name Microsoft.CredentialManager

    → press Enter.

    • Credential Manager window will open.
    1. Look for entries containing mail.comcast.net or smtp.comcast.net.
    2. Delete those entries.
    3. Reopen Outlook, enter your Comcast password, and select “Remember password”.

    This forces Outlook to rebuild a clean credential cache.

    3. Issues after sleep / restart

    (You must switch back to Outlook Classic to access the full POP advanced settings tabs)

    You mentioned that after “sleep,” Outlook hangs. This suggests TLS session or socket timeout issues. To fix:

    • In Outlook > Account Settings > More Settings > Advanced, disable “Leave a copy of messages on the server” (if your workflow allows). POP connections often freeze if server state is maintained.
    • In Device Manager > Network adapter > Properties > Power Management, uncheck “Allow the computer to turn off this device to save power.”

    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.

    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.
    • 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.

    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.
    • Sometimes you must reset your Comcast password, even if webmail still works, because the backend POP authentication may reject the old password.

    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".  

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread. 

    Please feel free to let me know if you have any further updates, thanks.

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.