They do NOT need to block the port. They just have to do like we do and
block any email from unknown users.....
(509) 982-2181 Equipment sales
(408) 907-6910 (Vonage) Consulting services
42846865 (icq) And I run my own wisp!
126.96.36.199 (net meeting)
----- Original Message -----
From: "Richard (Rick) Karlquist" <email@example.com>
To: "Steve Meuse" <firstname.lastname@example.org>
Cc: <email@example.com>; <K7LXC@aol.com>
Sent: Friday, September 08, 2006 9:33 AM
Subject: Re: [TowerTalk] Attn all comcast subscribers
> 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.
> Rick N6RK
>> -----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
TowerTalk mailing list