Visitor

 • 

3 Messages

Tuesday, November 18th, 2025 12:56 AM

IMAP issues with Comcast since Nov 9th

On Nov 9th, all of my devices quit syncing with Comcast.  I use WIndows Outlook 2024 pro and my iphone and Ipad.  The error I get on my PC is "we couldn't connect to the incoming (IMAP) server.  None of the authentication methods supported by Outlook are supported by your server"  I also received a security warning "The server you are connected to is using a security certificate that cannot be verified.  The target principal name is incorrect."    I then tried my Iphone and Ipad and received the error " Invalid username and/or password.  Please check your SMTP user name and password.

Actions taken

- Review and made sure the Incoming and outgoing mail servers were correct (Example imap.comcast.net (port 993,SSL enabled)

- I changed my password on comcast to see if that helped the process.  It did not.

- I tried on a different network, no luck

- I totally deactivated Norton Firewall when signing in...no luck

- Cleared the outlook cache.  No luch

- removed and tried to re-establish the account.  No change

I am at wits end and it has been extremely frustrating.  Any ideas to help

Oldest First
Selected Oldest First

New Poster

 • 

3 Messages

8 days ago

Same problem with IMAP from Outlook with intermittent server connection error; connection on smtp for outbound is fine.  IMAP didn't work for two days on one Win10/Office2021 PC and then suddenly downloaded and worked for 24 hours but not connecting again today for more than 6 hours;  Just now suddenly working again.  Very similar problem with Android cell; did not work for a couple of days and then suddenly downloading messages but quit again at 12:15AM today and still not connecting for inbound messages.  One other Win11/Office 2021 PC consistently works upload and download.  All settings are correct and have not been changed.   

Visitor

 • 

3 Messages

8 days ago

I had to switch to STARTTLS and port 143 to get it to allow me to add to Outlook Classic.  
Today, I was able to go back and change it back to SSL/TLS and port 993 and it continued working. 

This seems to be clearly something on the Comcast side.

Contributor

 • 

51 Messages

@user_qai923​ When you switched to STARTTLS and port 143 did it immediately resolve the issue and you could get incoming email?

Joe P

New Poster

 • 

12 Messages

No matter what mailer i use. Thunderbird or Outlook., with the forwarder with in Xfinity i only received half the mail. No matter what port or security preferences are set. I have to get them on directly on Xfinity account. Some days it works correctly, some days not.. Upon talking to a breathing agent, they did state, they are upgrading their network. Like last months bill. I couldn't even pay it online like i have done for the past 15 plus years. It is on their end. Waite and see is the only option. I just get burned out in an attempt Call after call after call. 

Visitor

 • 

3 Messages

7 days ago

And like that, with no explanation other than 4/5 days have gone by, it just works again.  If we're on "time out" punishments, I'd be nice to know that and not have to keep trying to get a connection that'll never materialize for another 5 days...

We know who's to blame, it'd just be nice they admit error..

Visitor

 • 

3 Messages

2 days ago

things were working.  Now I get the error "your server does not support the connection encryption type you have specified.  Try changing your encryption method."   

I've tried all various encryption methods.  Note:  This is for Outlook Classic 365.

Any ideas.  This is the yahoo mail   comcast account

New Poster

 • 

3 Messages

1 day ago

Here we go again.  After 5 days of everything working,  imap on multiple accounts doesn't download and just sits with finally an error "cannot connect to server contact server administrator or ISP".  Nothing wrong on this end with technology or ISP.    Last synchronization on Android shows 11PM yesterday.  Download works on one Win11 PC but same account does not download on Android or other PC using Outlook 2021.  

Visitor

 • 

3 Messages

Yep!  Me too!  Came back last week and it’s gone again today.  I guess we don’t check our email for another week till it mysteriously just “comes back”.   Moving to yahoo can’t come fast enough at this point…

Official Employee

 • 

956 Messages

1 day ago

Hey folks, 

I'm going to ask that if you're seeing an issue today (Dec 18th, 2025), could you please DM me some details about your configuration?  (Do NOT put it in a reply here, it will get flagged by a moderator for containing private information)

UserID(s) Impacted:
ISP or Mobile Carrier:
Email Client:
Operating System:

IP Addresses from whatismyipaddress.com (IPv4 and IPv6):
Knowningly using VPN or other Anonymity service: Y/N
Other details:



The "other details" could be something like:
* Mobile works on wifi, not on cellular
* Desktop is fine, mobile is not
* Doesn't work on VPN, works when disabled

* One user works, other user does not

Thanks folks.  I know this is frustrating, and we are working to find the best solution here.

Contributor

 • 

51 Messages

@XfinityAlex​ Thanks Alex.

My original post related to this same ongoing issue is not in this thread but here:

https://forums.xfinity.com/conversations/email/unable-to-recieve-outlook-email-but-can-get-webmail/6937111e8f5b6e1c4ab0ae92

Previously I was out for 5 days and  without any intervention the IMAP issue was magically resolved after 4 days.  I went back out again yesterday and as I stated I did not make any changes nor did I attempt to make changes which would cause this error and I got the same error as those in this thread:

Task 'xxxxxxx@comcast.net (2): Folder:Inbox Check for new mail.' reported error (0x800CCC0E) : 'Outlook cannot download folder Inbox from the IMAP email server for account xxxxxxx@comcast.net (2). Error: Cannot connect to the server. If you continue to receive this message, contact your server administrator or Internet service provider (ISP).

At this point I am counting the days to see if it again gets magically resolved as it has in previous posts going back 2 years.  This certainly is not a new issue.

Joe P

(edited)

forum icon

New to the Community?

Start Here