Comcast did not block this port until last month.
Then, without announcing it, they started blocking
it. I wasted a couple of hours trying to figure
out why I couldn't send mail all of a sudden.
Of course my ISP provides an alternate port.
> -----Original Message-----
> From: Steve Meuse [mailto:firstname.lastname@example.org]
> Sent: Friday, September 08, 2006 9:08 AM
> To: Rick Karlquist
> Cc: K7LXC@aol.com; email@example.com
> Subject: Re: [TowerTalk] Attn all comcast subscribers
> Rick Karlquist expunged (firstname.lastname@example.org):
> > One more thing: another dumb thing Comcast does is block the default
> > port used to send mail via your other ISP. You need to select
> > an alternate port. Make sure your ISP supports this.
> Blocking port 25 outbound is a *very* good thing. This prevents
> subscribers who have trojan spam bots on their machines from
> spamming the rest of the world.
> If you have an alternate mail provider that has any clue of what
> they are doing, they are using authenticated SMTP, which
> typically is not run on port 25.
TowerTalk mailing list