[at-l] AOL Blocking problems - some 'tech' stuff

[ryan at hack.net (Ryan Brooks)]

AOL told me this a long time ago, but it doesn't jive.  I think it's 
some sort of stock answer.

I've looked up my addresses on all these blacklist servers and they come 
up clean.  (I actually use one of these services to block some of the 
list spam).

Last time this happened, I got my ISP to fix a reverse DNS problem which 
cleared things up- but obviously they've added another layer to their 
filtering that I'm not aware of.

The good news is that I do have a fix for this, but I can't get it 
online this week.  Early next week w/ the new server should be the first 
opportunity.

-Ryan

Martin Fors wrote:

>This is a bit of information and hopefully you all will show some grace to
>AOL users in their problem.  BTW, Jack my friend, COMCAST has been proven to
>be the highest Spam processing ISP in the world.  Most Spammers use COMCAST
>as their ISP and spoof their sending from address:
>
>The problem could be that ATL-L's particular IP got onto dnsbl.us.sorbs
>blocking list.  AOL uses this, I believe, in their anti-Spam software.  This
>might have happened because either the ISP itself or someone else reported
>the IP as a Spammer.  Someone who does not like this list may have done it.
>They also could've used a netblock - which is confusing because that kind of
>block refers to a range of domains rather than the act of blocking an
>individual IP, and ATL-L's IP got accidentally gobbled up by it.  I don't
>know if that has been the case.  It is used to block dynamically-assigned
>IP's.  If you're interested DNSBL gives a long blurb about justifying what
>they do.  It's quite hard to get off their s--t list.
>
>http://www.dnsbl.us.sorbs.net
>
>rusty
>_______________________________________________
>at-l mailing list
>at-l@backcountry.net
>http://mailman.hack.net/mailman/listinfo/at-l
>
>  
>