Author Topic: Comcast blocked my port 25 (Read 1884 times)

Czar · « **on:** July 30, 2009, 07:38:37 AM »

Quote

In an effort to help prevent spam and ensure the security of our network and customers, Comcast has modified your modem’s settings to prevent the sending of email on port 25. That is the default port email programs such as Outlook Express use to send email. We’ve taken this action because we may have detected virus-like activity from your modem or received reports from other email providers that mail from your modem generated complaints from their users.

Bummer.. I run a linux box that hosts my website and MOOs, both of which send mail from time to time.

So am I humped? Is there something I can do in my router to change port 25 traffic over to port 587? (the port suggested in the rest of the comcast email)

Five Aces · « **Reply #1 on:** July 30, 2009, 03:39:23 PM »

port triggering/forwarding is usually inbound but you might be able to work something. I'd say the problem is no one is really gonna accept email on 587 like 25(except comcast's secure connection). Having worked there and rebuilt accounts for customers, I'd say good luck with the abuse department. The work around is (SHhhh) down grade your account to the slower service, call back the next day to upgrade and the Abuse code for blocking port 25 won't be on your account. I'm not sure if the Sully can comment on this since he still works there.

Czar · « **Reply #2 on:** July 30, 2009, 03:45:51 PM »

Eh if they want to block port 25, let em. I don't need to receive mail, just send it.

Five Aces · « **Reply #3 on:** July 30, 2009, 03:47:13 PM »

thats the port it sends on

http://www.mailsbroadcast.com/email.broadcast.faq/33.port25.blocked.email.faq.htm

Czar · « **Reply #4 on:** July 30, 2009, 03:47:49 PM »

Yeah. Teh Suxx0r

The Nstuff · « **Reply #5 on:** July 30, 2009, 05:54:49 PM »

that's hardcore. Is there a reason why you can't use comcast's secure port? Are you running a mailserver that thus needs to communicate with other mail servers?

If you are just using sendmail client or something, what's the problem? Comcast's servers will then forward it on to the standard port so your e-mail gets to it's intended target.

BTW Czar, there was a dude on TF2 server last night that sounded exactly like you. Can't remember his handle.

sully! · « **Reply #6 on:** July 30, 2009, 06:08:18 PM »

I have no input on the issue. I don't do anything with customer facing services. I am all internal services.

Agent4054 · « **Reply #7 on:** July 30, 2009, 06:09:07 PM »

Quote from: nstuff on July 30, 2009, 05:54:49 PM

BTW Czar, there was a dude on TF2 server last night that sounded exactly like you. Can't remember his handle.

I think that was spitfire

The Shoctor · « **Reply #8 on:** July 30, 2009, 07:14:20 PM »

Quote from: Agent4054 on July 30, 2009, 06:09:07 PM

Quote from: nstuff on July 30, 2009, 05:54:49 PM
BTW Czar, there was a dude on TF2 server last night that sounded exactly like you. Can't remember his handle.

I think that was spitfire

QFT

Czar · « **Reply #9 on:** July 30, 2009, 08:01:25 PM »

my linux server only sends mail out, from my blog, a CMS i have hosted for someone else, and a series of MOOs (MUDs) that send new players emails containing their password.

What may have set it off was that for the past...2 years..Ive been emailing 15 megs worth of attachments every Thursday morning at 3am - backups of the MOO/MUD files to the game owners.

sully! · « **Reply #10 on:** July 30, 2009, 08:21:18 PM »

I tried to find some specifics for you on what triggers the port 25 block. This is all I could find:

Quote from: http://customer.comcast.com/Pages/FAQViewer.aspx?Guid=d3609bda-26c4-4200-a9ba-ba991251a9f6

Port 25 is an unsecured port on a computer that those sending spam can take control of to send spam - often without the user ever knowing his/her computer has been compromised. When spam from a compromised computer is detected, Comcast’s anti-spam systems automatically apply a sending block and send an email notification to the affected subscriber’s comcast.net email address. This block does not interrupt mail service for Webmail (e.g. Comcast, Yahoo, Gmail, or Hotmail); however, this block does prevent email programs or clients (e.g. Outlook Express) from sending email. Client e-mail programs will still receive email. The instructions at our mail client help page explain how to configure common email client programs to use Port 587, which includes authentication, instead of Port 25.

You are a well-versed user of the Tweets. Maybe @comcastcares can help you out (or one of the others listed on the left side of the background image at http://twitter.com/comcastcares) on understanding what specifically caused the block, as the above indicates the blocking mechanism is automated.

Czar · « **Reply #11 on:** July 30, 2009, 08:28:17 PM »

Sounds good. I`ll check in to it. Thing is, I shouldnt be running a server on a residential account anyways so I may just leave it alone.

_!Rathe!_ · « **Reply #12 on:** July 30, 2009, 08:46:12 PM »

Why not get a free SSL certificate and use that to send mail to the other servers on port 587?

The Shoctor · « **Reply #13 on:** July 31, 2009, 08:47:44 AM »

Depends on if the server he is sending to will accept on that port and/or accept SSL connections. (RE:Bad Firewall Config.)

Author Topic: Comcast blocked my port 25 (Read 1884 times)

Czar

Comcast blocked my port 25

Five Aces

Re: Comcast blocked my port 25

Czar

Re: Comcast blocked my port 25

Five Aces

Re: Comcast blocked my port 25

Czar

Re: Comcast blocked my port 25

The Nstuff

Re: Comcast blocked my port 25

sully!

Re: Comcast blocked my port 25

Agent4054

Re: Comcast blocked my port 25

The Shoctor

Re: Comcast blocked my port 25

Czar

Re: Comcast blocked my port 25

sully!

Re: Comcast blocked my port 25

Czar

Re: Comcast blocked my port 25

_!Rathe!_

Re: Comcast blocked my port 25

The Shoctor

Re: Comcast blocked my port 25