[sllug-members]: Comcast Blocking Port 25?

[u235sentinel]

Personally I vote for "Hanging up on Comcast" but I'm biased :-)

Of course this idea should work ok unless they do a packet inspection. 
You never know :D



Clint Savage wrote:
> I personally have not experienced this problem and I've had Comcast for 
> some time.  However, I can give you some simple solutions that might 
> help you in the short term.
> 
> There are two ways to solve this problem.  One is simply quitting 
> Comcast, and that might not be your desired option.  The other is to set 
> up some sort of routing around the problem.  Yes its a pain, but 
> actually not that hard.  I used iptables to set up a redirect rule on my 
> mail server; something like this:
> 
> iptables -t nat -A PREROUTING -i eth0 -s my.client.ip.addr --dport 2525 
> -j REDIRECT --to-ports 25  - This rule will accept anything on port 2525 
> and redirect it to port 25.
> 
> then on my client system, the one that's getting blocked, set up your 
> MUA (Thunderbird, Evolution, whatever) to send over port 2525 for SMTP 
> rather than 25.  If that won't work for you, use iptables to reroute it 
> to port 2525
> 
> iptables -t nat -A OUTPUT -o eth0 -d my.mail.server.ip --dport 25 -j 
> REDIRECT --to-ports 2525  - This rule will accept anything on port 25 
> and redirect it to port 2525.
> 
> That's close and with a little tweaking should work for you no problems.
> 
> Cheers,
> 
> Clint
> 
> On 3/19/07, *Jeff Day * <jd at clickworks.com <mailto:jd at clickworks.com>> 
> wrote:
> 
>     Hi All,
> 
>     I guess I'll chime in with a question.....anyone have a problem sending
>     email thru port 25 over Comcast cable? Several weeks ago all outgoing
>     traffic on port 25 was blocked...through their on-line, chat, support
>     person says they don't do that.
> 
>     Any input is welcome.
> 
>     Thanks,
> 
>     Jeff
>     ____________