[TriLUG] OT? - RR now blocking email from dynamic IPs...

[C.Magnus Hedemark]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


On Monday, June 16, 2003, at 11:54 AM, John Franklin wrote:

> Hmm... I wonder if citing the inappropriate blockage as a service 
> breach would do it.  TW RR customers would have to file the complaint 
> as it their service being denied.  If they're blocking from 
> businesses, they might be able to claim loss of business.

Check your TOS before complaining;  most residential broadband services 
use broad language to say more or less "no servers".  While I think our 
understanding of the intent is to not allow incoming connections to 
servers on residential connections, in light of something like this it 
could be interpreted as *any* server running that makes use of TW/AOL 
bandwidth resources.

IMHO AOL/TW shouldn't be blocking email originating from within their 
own network to destinations within their own network.  After all, they 
know who owns what IP address and can take full action if any abuse is 
going on.  I think a sufficient approach for them to take instead of 
this one would be if they would only accept mail after they have probed 
a host and checked to see if it were an open relay or not.  If a host 
is not an open relay, then by all means accept mail from it.

IP's originating outside of their own network is a harder sell, mostly 
since they don't have any control over those IP's, but blocking *all* 
broadband dynamic IP's is foolish.

The people who have more right to complain, IMHO, are the *@aol.com and 
*@*.rr.com users who have had inbound email blocked against their 
wishes.

- --

Magnus Hedemark
"From the Fury of the Norsemen please Deliver us, Oh Lord"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (Darwin)

iEYEARECAAYFAj7t6+8ACgkQYPuF4Zq9lvad2ACdHIZLA74yw+sFkWR/4E9Wax/B
BX8An0YM1i8GPpsq8dkuVlaeyXrld7kI
=c+cS
-----END PGP SIGNATURE-----