Sucky Comcast/Microsoft

[Ken Ibold]

Ack!

After years of my email working flawlessly, today it decided to give up the ghost. I can receive mail, but I cannot send it. This is affecting multiple computers, so I gather it's not just the settings on one.

The error messages I get are

Error 0x80042108 "The operation timed out waiting for a response from the sending (SMTP) server. If you continue to receive this message, contact your server administrator or internet service provider."

Which is followed in a minute by

Error 0x80042109 "Outlook is unable to connect to your outgoing (SMTP) server. If you continue etc."

Comcast says they are not allowed to support Outlook.

Any ideas? Could this be a router (Linksys wireless) issue?

 

[SkyHog]

Ack!

After years of my email working flawlessly, today it decided to give up the ghost. I can receive mail, but I cannot send it. This is affecting multiple computers, so I gather it's not just the settings on one.

The error messages I get are

Error 0x80042108 "The operation timed out waiting for a response from the sending (SMTP) server. If you continue to receive this message, contact your server administrator or internet service provider."

Which is followed in a minute by

Error 0x80042109 "Outlook is unable to connect to your outgoing (SMTP) server. If you continue etc."

Comcast says they are not allowed to support Outlook.

Any ideas? Could this be a router (Linksys wireless) issue?

Most likely, you've got a problem with the SMTP server....here's what to check:

The outgoing mail server should be:
smtp.comcast.net

Not mail.comcast.net nor any other regional smtp server.

Also, make sure "My outgoing (SMTP) requires authentication" is checked

Qualification: I used to work for Comcast. We supported Outlook. lol. Apparently things changed.

 

[mikea]

Ack!

After years of my email working flawlessly, today it decided to give up the ghost. I can receive mail, but I cannot send it. This is affecting multiple computers, so I gather it's not just the settings on one.

The error messages I get are

Error 0x80042108 "The operation timed out waiting for a response from the sending (SMTP) server. If you continue to receive this message, contact your server administrator or internet service provider."

Which is followed in a minute by

Error 0x80042109 "Outlook is unable to connect to your outgoing (SMTP) server. If you continue etc."

Comcast says they are not allowed to support Outlook.

Any ideas? Could this be a router (Linksys wireless) issue?

Sure. (Guessing here.) Comcast just rolled out a block on port 25 to kill off spam bots. Try looking up help on Comcast's web site to see if they tell you to use a different port, or maybe you can use SSL. You change the port the Accounts window.

What's amazing is them refusing to support Outlook. What are you supposed to be using? Lemme guess. They have their own client that has 3/4 of the screen full of ads.

 

[CJones]

Ask Comcast for their mail server settings (servers, ports, etc.). It's possible they changed something and didn't find it necessary to notify the end users.

 

[Ken Ibold]

Sure. (Guessing here.) Comcast just rolled out a block on port 25 to kill off spam bots. Try looking up help on Comcast's web site to see if they tell you to use a different port, or maybe you can use SSL. You change the port the Accounts window.

What's amazing is them refusing to support Outlook. What are you supposed to be using? Lemme guess. They have their own client that has 3/4 of the screen full of ads.

I can't find the port info in the accounts window. Where is it?

Edit: Nevermind. Found 'em.

 

[billwil]

Ken...are you all fixed? If not, let us know where you're at in the process...we'll get you all patched up.

 

[Ghery]

I had a problem with Comcast e-mail a while back. Here is the e-mail they sent, along with instructions on how to set Outlook so it would work. I hope this helps.

Dear Comcast Customer:
ACTION REQUIRED: Comcast has determined that your computer(s) have been used to send unsolicited email ("spam"), which is generally an indicator of a virus. For your own protection and that of other Comcast customers, we have taken steps to prevent further transmission of spam from your computer(s).
Comcast.Net WebMail Users
If you use a web browser to access your email, this change will not affect your service. However, it is important that you take steps to remove the virus and secure your computer(s). This can be done by using the FREE McAfee Antivirus and Firewall software available from Comcast on the Comcast Security Channel or by using other popular antivirus solutions that are widely available.

Third-Party Mail Client Users (Outlook, Outlook Express, etc.)
If you use Outlook Express, the steps we have taken to protect the Comcast network will not allow you to send email until you apply a simple one click fix available at http://www.comcastsupport.com/alternateport. While this will restore your ability to send mail it is still important to remove any possible viruses from your computer. This can be done by using the FREE McAfee Antivirus and Firewall software available from Comcast on the Comcast Security Channel at or by using other popular antivirus solutions that are widely available. Note: this one click fix currently only works with Internet Explorer. If you use a different browser, please visit http://www.comcast.net/help/faq/TB25 for steps to manually change your port.
If you are using a third-party client other than Outlook Express (Outlook, Eudora, Thunderbird, etc.), please visit http://www.comcast.net/help/faq/TB25.
Comcast is focused on providing a secure internet experience for all of our customers. Please visit the Comcast Security Channel regularly to stay up to date with the latest security threats, products, and services
If you have additional questions please visit (www.comcast.net/help).
Thank you for choosing Comcast!
Sincerely,
Comcast Customer Security Assurance

 

[Ken Ibold]

Following links that were on Ghery's pages, I found a reference to changing to port 587, which worked on all machines.

Thanks, guys!!!!

 

[mikea]

Following links that were on Ghery's pages, I found a reference to changing to port 587, which worked on all machines.

Thanks, guys!!!!

Heh. Port 587 is what yahoo uses, too. I guess it's the official unofficial alternate port for SMTP. I should have suggested that.

Now, how hard izzit for the spam bot writers to add a try on port 587 to the code?

 

[mikea]

I had a problem with Comcast e-mail a while back. Here is the e-mail they sent, along with instructions on how to set Outlook so it would work. I hope this helps.

Dear Comcast Customer:
ACTION REQUIRED: Comcast has determined that your computer(s) have been used to send unsolicited email ("spam"), which is generally an indicator of a virus. For your own protection and that of other Comcast customers, we have taken steps to prevent further transmission of spam from your computer(s)....

That's a berry, berry bad thing if it's true, but I'd trust Comcast to not have it be true.

I hope you ran adaware and virus scanners to find if there is really is anything running.

Better yet, run a sniffer on your network to see who it's talking to.

 

[jesse]

Heh. Port 587 is what yahoo uses, too. I guess it's the official unofficial alternate prot for SMTP. I should have suggested that.

Now, how hard izzit for the spam bot writers to add a try on port 587 to the code?

It is fairly common for providers to separate MSAs and MTAs (Mail Submission Agents versus Mail Transport Agents). The MSA is for user submitted mail and the MTA is for mail coming from other servers bound for a user that it hosts e-mail for.

As per RFC4409--port 587 is to be used for MSA specific servers.

Now to answer your spammer question--when an ISP blocks outbound port 25 (many of them do) they are trying to stop their users from becoming spam bots when they get infected w/ spam. They don't generally touch port 587 because as per the above most servers will only be running 587 for MSA work and not MTA work.

Since Yahoo is a smart company they realize that many providers block port 25. In order to get around this they set their MSA servers to run on 587 per the spec.