Comcast Blocking Port 25 Without Notice (Updated)

Comcast this weekend did something nice to me (not). They blocked my Port 25, without any notice at all.

Now, I don’t use port 25 on most email accounts, I use SSL email over port 587. But, plenty of people do use it.

Worse, Comcast Tier 2 support hasn’t been informed that they are blocking port 25, nor do they have any idea of what to do if your email provider relies on Port 25 (as in, you can’t use another port).

Port 25 blocking has become a popular way to reduce the tide of spam and viruses, which commonly use Port 25. The majority of major ISP customers use web mail, and as such aren’t impacted by these blockings.

Now, I don’t know if I’m simply unlucky, and this is a glitch on my account… or if this is the start of a company-wide move. So, let me know if Comcast is blocking Port 25 on you in the comments.

Update: Looks like I’m definetely not alone. If you see this posting [note: profane language], the comments start around early April, and new Port 25 blocks run through this week. Clearly, Comcast is deploying new Port 25 blocks, and clearly they have no protocol for unblocking.

That’s not good Comcast, I’ll give it (my trouble tickets) a week, then it’s FCC Complaint time.

Trackback | Permalink |

22 Comments on “Comcast Blocking Port 25 Without Notice (Updated)”

Daniel H. on May 12th, 2008, 12:22 pm  

sorry man, i’ll pretty much always use webmail for this sort of reason. what if i move and change providers? that sort of thing never quite sat well with me.

Christopher Price on May 12th, 2008, 12:49 pm  

I for one never use webmail systems… they’re unreliable and less secure. Someone shouldn’t make email choices based on an internet provider’s faulty implementations… instead, we need to pressure Comcast to fix this.

The line of thought is dangerous, since one could say that you shouldn’t innovate new technologies (BitTorrent) since Comcast “might” block it.

Thanks to IMAP, I can take advantage of the benefits of webmail (having all your email on every device) combined with the benefits of a desktop client (address book integration, spelling and grammar check, and searching inside of every email via file search… Spotlight on Mac, and Windows Desktop Search on PC).

AT&T had similar issues when they blocked Port 25. Now all it takes is filling out a form to unblock via request on AT&T.

Ken Anders on May 16th, 2008, 11:09 am  

Comcast just blocked me as well. I cannot stand that they do this without notice. Someone spoofed my email but there are not background email transfers running from my systems and I am not a spammer. If you have any suggestions on using Outlook to a safe SMTP mail server, that would be great.

Christopher Price on May 16th, 2008, 4:50 pm  

If your email provider supports SMTP with SSL, you can try turning that on and using port 587. Comcast certainly isn’t blocking that port…

However, if your email provider doesn’t support that, your only option is to call your email provider and hope that they have opened a secondary port.

Ian Argent on May 19th, 2008, 9:12 am  

I’ve been port-25-blocked for quite some time now. My provider supports a couple of alternate ports, so I just chalked it up to security and wen ton. It’s not like Comcast is any kind of innovating here - Cox has been blocking port 25 for quite some time.

Dan on June 4th, 2008, 8:35 am  

Comcast started blocking port 25 for us (Savannah, GA) last night–6/3/2008.
Their tech support was very unhelpful as usual, but I did wast about 2 hours with them.
I finally got around it for now by switching to port 587, but I think it’s more than time to check into alternative Internet suppliers.
I don’t like companies that arbitrarily restrict my usage like that.

Teri on June 7th, 2008, 4:01 am  

I had the surreal experience this past week of suddenly being unable to send mail from either of two “mail.com” accounts I have–both of which are set up for pop3 access through my Outlook2007. Comcast is my ISP.

After scrutinizing my Outlook settings, I noticed my Comcast email account had a port setting for 587 (SMTP) and my other accounts were on 25. Since I couldn’t get a live person for my other email accounts (and I HATE dealing with Comcast), as a lark I tried changing the SMTP ports for the “problem” accounts to 587.

Voila, and “hmmmm”. I called Comcast, who claimed they had switched ports months ago and couldn’t imagine why I was having trouble all of a sudden. I suspect they switched mine at the exact time I started having problems and didn’t tell me. Worse, it looks like they are now lying about it.

I freakin’ HATE dealing with Comcast. If you get a friendly AND knowledgable person, you are lucky.

Teri

Teri on June 7th, 2008, 4:06 am  

One more thing…

I don’t have a problem with their blocking the port, but I DO have a problem with their not notifying customers so they can prepare. That’s just plain rude.

It’s like cutting off any utility with no notice as to what the problem is.

Teri

ZOOM on June 12th, 2008, 2:58 pm  

Hi,

Some ISP’s such as comcast are starting to block the default SMTP port 25. As an alternative you can try port port 587 … to do this try smtp.domain.com:587 or mail.domain.com:587.

Another option is to configure your server to use a free SMTP outgoing service like gmail make sure to use SSL for port 587

Incoming Mail (POP3) Server - requires SSL: pop.gmail.com
Use SSL: Yes
Port: 995
Outgoing Mail (SMTP) Server - requires TLS: smtp.gmail.com (use authentication)
Use Authentication: Yes
Use STARTTLS: Yes (some clients call this SSL)
Port: 465 or 587
Account Name: your Gmail username (including @gmail.com)
Email Address: your full Gmail email address (username@gmail.com)
Password: your Gmail password

michel on June 18th, 2008, 6:02 pm  

Well I have been block on inbound 25 yesterday
Calling Comcast they says this is a VIOLATION of the policy to have an email server on a residential plan

Grrrrr… there is no way around !

Ben on June 21st, 2008, 2:15 pm  

Blocking 25 in Northwest

mb on June 23rd, 2008, 11:09 pm  

25 blocked here in the East Bay area of San Francisco Bay

mb on June 24th, 2008, 12:04 am  

it’s about midnight, and suddenly 25 is unblocked…..go figure….I’m it sure it isn’t a case of Comcast’s decency to its customers or bowing to public outcry. Am sure it’s caprice…….again.

Is anyone else “cured”?
mb

Ray on June 24th, 2008, 10:15 am  

My comcast account became blocked and I switched to port 587 after surfing various forums like this one. Although some say port 465 works for outgoing (along with ‘my server requires authentication’ which I’ve never needed in the past).

I fear that many of my web design customers will have same problem. Just got call from one with same problem, but he uses Verizon, so it only gets worse. My Host can’t give me good suggestion.

Bonnie on June 25th, 2008, 8:23 am  

Hey-
My comcast account is blocked (chicago) for outgoing email- and I am just now educating myself on this whole issue- kind of a newbie. Is there anyone out there who can fill me in on the issue of ‘open relay’? I would like to be able to find out if my account is being used so I can fix that. I am a Mac user- any help would be greatly appreciated. Seems to me, a better solution to the whole spam issue would be to help consumers safeguard their accounts to keep the spammers out- rather than just blocking everyone. I am not an expert by any stretch of the imagination, but it just seems like laziness on the part of the ISPs…

Thanks.
Bonnie

Mike on June 30th, 2008, 5:11 am  

Comcast in the Boston area starting blocking ports this weekend, yesterday I think (6/29)!

They are blocking BOTH inbound AND outbound SMTP AND they are blocking relays through their SMTP servers. Ugh, I’m about to get on the phone with them and NOT looking forward to it.

The thing that really ticks me off is I have both residential and commercial accounts with them. The commercial account has static IPs. I wanted to get COMMERCIAL internet with RESIDENTIAL phone and TV (because you can’t get premium TV channels on a COMMERCIAL account) and they couldn’t configure my account that way! In their pea-brain world you have to be EITHER a Reisdential OR Commercial customer (I guess they haven’t quited grasped this whole “running a business at home” thing just yet…..!!!).

-Mike

Dan on June 30th, 2008, 8:54 am  

Comcast started blocking me in Boston between 1:00AM-6:30AM on 06/28/08, inbound and outbound on port 25. I’ve run my mail server for my business at home for years. The dynamic ip only changed once maybe twice a year.

I just called Comcast and ordered a static ip commercial service. They didn’t seem to have any problems with two bills going to the same address. (residential tv and commercial internet)

Ray on July 17th, 2008, 10:49 am  

Here’s a possible fix. It worked for me (at least for now) for one of my webmail “added” accounts. I got this from a comment at http://www.lockergnome.com/usrbingeek/2007/04/12/comcast-blocking-port-25/

In Outlook, go to: Tools..Email Accounts..(select one)
Double click the email acct you want to alter
All email accounts must have smtp.comcast.net as the outgoing mail server.
Click More Settings..Outgoing Server tab
Check My Outgoing Server requires authentication
Check Log On Using and type in your Comcast username and password.
Click Advanced tab and change your Outgoing Server to 587
Click OK and then click Test Account Settings and you’ll be fine.

Chuck on July 18th, 2008, 8:52 am  

After reading these forums concerning Comcast’s port 25 issue, it seems that we may need to be more specific on the “mail server” location and access point.

What I mean is, some people say that Comcast is blocking their server from sending mail, where is the server? Is the server actually in your home or are you using a server at a remote location/company like ipower or godaddy?

Comcast can not block the remote server. They can only block your computer at your home (IP) when using a third party mail program such as outlook. What I am saying is that they are interrupting your communication with your server when you are trying to send mail. Your web mail works because you are sending from the server which is not using comcast and not from your computer which is.

Today I filed complaints with the FCC and the New Jersey Board of Public Utilities. I hope everyone here will take the time to do the same.

Comcast is using their monopoly power for social engineering. Comcast decides what we can and can not use the internet for. The FCC has just fined or is about to fine comcast for its practice of blocking file transfers they didn’t like.

I am not a lawyer but maybe comcast’s interference with us doing business with our server providers is an abuse of their monopoly power and a violation of the anti-trust laws.

Obviously, I would like to hear everyone’s thoughts on what I have written even if you disagree.

I think that I will pursue the legal concept of comcast’s violation of the anti-trust laws.

B.M. on July 24th, 2008, 7:17 pm  

Grrrr . . . I just uncovered this issue. I’m totally annoyed and clueless. So if my e-mail is bm@comcastihateyou.com how am I supposed to send if I can’t use the outgoing comcast server anymore and I’m using something like gmail? Any suggestions in non techie speak?

Stan on August 1st, 2008, 7:51 am  

Just started getting outbound email blocked (worked fine until now). I have mail using GoDaddy domain, now can’t logon to smtp.comcast.net. port 587 Comcast helpdesk says that I have to use mail.comcast.com as my POP3. tried to get a supervisor, but was told they were busy. anyone find a solution to this?

Michael on August 2nd, 2008, 5:47 am  

Stan, try using port 80 for your Godaddy email account. I found that suggestion of the GoDaddy website and it fixed my problem.

Leave a comment