Tired of Being Screwed By Cox (no pun intended)

[David A. Sinck]

\_ SMTP quoth Chad and Shaun Horton on 6/17/2003 14:55 as having spake thusly:
\_
\_ The bright folks at Cox have struck us with another one of their
\_ brilliant ideas again. Apparently the Cox put a jimmy hat on port 25. 
\_ Do you have an smtp server and also subscribe to Cox (http://www.cox.com
\_ and http://www.cox.net)? Well, you poor sap. You are no longer allowed
\_ to send email through your smtp server because Cox, in their infinite
\_ wisdom, has now blocked port 25. This includes both servers within your
\_ local network AND hosted by an external provider.

If you have root on the remote smtp server its quite easy to step
around their filter on any port given recent linux kernels on both
sides.

I think the auth requirement of 'resolveable domain' is weak.  

From support@cox.net
Subject: I love spam
[....]

See, that resolves JUST FINE and doesn't prevent me from sending
spam.  Pick a dictionary word, then do a quick whois and you're in
downtown.  

Unless, of course, they notice high volume from a single host.  But in
theory, they should be able to notice high outbound connects to 25
even if they aren't the destination host.  They do control the
horizontal and vertical on the bandwidth, after all.

YMMV.

David