imap.comcast.net is not responsive

[sbrozell]

Hi,

Please resuscitate imap.comcast.net:

===

$  ping imap.comcast.net
PING imap.ge.xfinity.com (96.117.3.125) 56(84) bytes of data.
^C
--- imap.ge.xfinity.com ping statistics ---
16 packets transmitted, 0 received, 100% packet loss, time 14999ms

===

For context see, https://www.xfinity.com/support/articles/email-client-programs-with-xfinity-email?view=app

thanks.

[BruceW]

---

@sbrozell wrote: ... Please resuscitate imap.comcast.net: ...

---

This is likely deliberate. Servers are often set to ignore ping and trace packets. But imap.comcast.net is responding to mail clients, so it's doing its job.

[sbrozell]

Hi,

imap.comcast.net is not responding to my email client since Tuesday morning.  In addition, i do get a ping from smtp.comcast.net, their outgoing mail server, and i am able to send email.

scott

[BruceW]

At a command prompt, do you get a response to

        telnet imap.comcast.net 110

?

I get "+OK Dovecot ready".

[sbrozell]

Hi,

Thanks, there is progress, but my email client still cannot read my inbox.  telnet connects on port 110, but it's not clear what is happening on the Incoming Mail Server Port Number 993, which my email client had been using and is specified in the comcast documentation.  telnet connects to the other port in the doc. 143 and the output indicates this is an imap connection, but my email client fails using 143.  I am updating my email client software just in case.   Please send verbose and verbatim details on how your 3rd party email client is connecting via imap.

scott

ps details:

$ telnet imap.comcast.net 993
Trying 96.118.208.102...
Connected to imap.comcast.net.
Escape character is '^]'.
^C^C^CConnection closed by foreign host.

$ telnet imap.comcast.net 143
Trying 96.116.224.176...
Connected to imap.comcast.net.
Escape character is '^]'.
* OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE LITERAL+ STARTTLS LOGINDISABLED] Dovecot ready.
^C
^C
^C
Connection closed by foreign host.

$ mutt
Reading imaps://imap.comcast.net:143/...
Looking up imap.comcast.net...
Connecting to imap.comcast.net...
gnutls_handshake: An unexpected TLS packet was received.

[sbrozell]

Hi,

The third party email client software update worked !

Thanks to BruceW.

scott

[ST_94]

I'm having the same issue since Tuesday. I'm running Outlook 2016 using imap port 993. SMTP is working just fine. Did you change clients to fix your issue?

[sbrozell]

Hi,

No i changed the version of my client from

Mutt 1.5.21 (2010-09-15)

to

Mutt 1.9.4 (2018-02-28)

scott

[ST_94]

Were you able to get your email working?

My email stopped working at the same time with the same symptoms. I run Outlook 2016 though. I was finally able to diagnose that it was due to not having IPv6 enabled on my Ethernet card. Once I checked that box it started working again. If I uncheck it, it goes back to not working again. To me it seems like something is wrong in the IPv4 path to imap.comcast.net. I have communicated with support about the issue but they do not see an issues so are not investigating further.

Give me a thumbs up if this was your issue as well.

[sbrozell]

Hi,

Yes, my email is working.  Changing my email client version fixed it.  My client is mutt, not outlook.

scott