MichaelCA's profile

Contributor

 • 

257 Messages

Monday, May 3rd, 2021 10:03 PM

Closed

Emails stopped forwarding from Comcast server

For some reason, I have been getting sporadic response from Comcast's email server.  This has been happening for several days now.  Sometimes I get timeout messages.  Sometimes I don't see the emails from Comcast for hours.  I am running Thunderbird (latest version) on Windows 10 Pro.  Attempting to send an email yields a timeout message on smtp.comcast.net.

This conversation is no longer open for comments or replies and is no longer visible to community members.

Expert

 • 

31.9K Messages

4 years ago

@MichaelCA 

See if this post applies to you.

Also, have you recently logged in to webmail?  You might want to do that just to make sure everything there is okay.

Contributor

 • 

257 Messages

Webmail (direct to comcast.net) works.  I could see several unread emails there, some a few hours old.

Extra information:  If I reboot my PC, I can get Thunderbird to work initially, but it goes back to being blocked rather quickly.

I attempted to send an email from a Comcast account (via Thunderbird), but I kept getting the smtp timeout message.  On a whim, I disabled my anti-virus software, and I was able to send the email.  Re-enabling my anti-virus software blocks emails from going out again.  Not sure why this is happening now.

Expert

 • 

31.9K Messages

Did you check the link I posted?

FWIW, Comcast scans all incoming and outgoing emails.

I am not a Comcast Employee.
I am a Customer Expert volunteering my time to help other customers here in the Forums.
We ask that you post publicly so people with similar questions may benefit from the conversation.

Was your question answered? Please mark an Accepted Answer!tick

Contributor

 • 

257 Messages

Doesn't appear to have been our issue.  It appears to have been a disconnect between the anti-virus software and Thunderbird.

The fix (for now) was to disable IPv6 in Thunderbird.  Hopefully there aren't security ramifications for doing so.

(edited)

Contributor

 • 

257 Messages

Further researching seems to indicate this issue does trace back to Comcast.  Apparently some of their servers are configured properly for IPv6 and some are not.  I guess the ones I need are not.  The problem with my solution is I won't know if Comcast will have corrected this.

Contributor

 • 

257 Messages

My last two responses describe what the source of the problem is and a workaround, for now.  I can't mark my own posts as a "solution", so I can't close this thread.

forum icon

New to the Community?

Start Here