#Comcast incoming mail server password upgrade#

This upgrade from Comcast, is a Generic Piece of crap. She skirted the main issue and she acted like you can’t understand me so I hung up on her. In fact she sounded more like a Politician. I spoke with some of their Tech people and one of the gals acted like she is teaching a Kindergarten class on what emails should look like. Thanks Comcast, for valuing our time so very little, in your quest to make mega millions. I tried once before in 2005 after nearly an entire summer of poor Comcast connectivity. If there was any competing product in my market I would switch in a heartbeat. One can only guess how many individual users are still frustrated at this very moment because they are being forced to do their business e-mail from home using their accounts, after uninformed Comcast agents are able to help them?Īs a web host, we were forced to spend hours dealing with Comcast before we got an actual answer, and we still lost a couple of hosting customers over it, who were convinced that it must be our fault, since Comcast told them it was. Instead, it takes the end user hours of frustrating time on the phone spent with lower-level tech-support who have no idea that this change has even taken place. This has been going on around the country for MONTHS. The problem with Comcast doing this is that they do not seem to be telling all of their support people, and do not be notifying their customers. I suspect they are really doing it to limit liability for any future potential lawsuits, and not really to save bandwidth, but I have no problem with that. The reason Comcast claims to be doing this is in an effort to prevent spam being sent by zombie/spyware/virus laden computers using their bandwidth and their Internet connection.

Choose Properties box – Advanced Tab – and from there you can do the same.

They did not check the “this server requires an encrypted connection” box.

Added note from comments below – Some people in the midwest for whom 487 didn’t work succesfully chaged to 465 and picked SSL under the “use the following type of encrypted connection” drop down.

Change your default port 25, to port 587, and you should be back in business in most cases.

Go to the more settings button, and into the Advanced tab.

Sselect the appropriate mail account and hit the change button.

Go to tools – e-mail accounts – view or change existing account.

In most cases, this seems to be port 587 for Portland providers. To cut to the chase, here’s the solution:Ĭhange the port your computer is using for SMTP outgoing mail, from Port 25 to one that your hosting provider will allow. This month, it’s apparently Portland Oregon’s turn, where I live. To make matters worse, users are finding out one at a time, because Comcast is slowly rolling out these changes user by user in individual markets around the country. After wasting time calling your web host, and going through various troubleshooting techniques, they tell you to call Comcast. If you are using for your SMTP outgoing mail server, then you get an error saying “unable to connect to the mail server” even though it just successfully connected to the mail server to retrieve your incoming mail. Account: ‘XXXX’, Server: ‘’, Protocol: SMTP, Port: 25, Secure(SSL): No, Socket Error: 10060, Error Number: 0x800CCC0E The error message says (fill in your own X): Users all over the country are finding out daily that suddenly, for no apparent reason at all, they are unable to send mail if they want people to reply to their business or personal e-mail addressed other than one that is This is because Comcast is blocking port 25, which is your default port for sending email through your mail software.

#Comcast incoming mail server password free#

This industry changes FAST, so blindly following the advice here *may not* be a good idea! If you're at all unsure, feel free to hit me up on Twitter and ask.

I post at now, and this post was published 15 years 2 months 19 days ago.