that the AHBL admits to using collateral damage entries, it is a key point in *not* using their lists, or not using their collateral lists.. if they have them as a separate item (haven't looked into AHBL other than to know I'd never use *them*).
The AHBL, based upon it's public listing policies, immediately added Mr. Scoville's SMTP server to our ban. Mr. Scoville responded with a legal threat in October 2003, which escalated his SMTP server to a different listing policy for spammers who use threats of violence or legal action. Due to the severity of such a threat, it was determined that Mr. Scoville would be escalated to our "Shoot on Sight" (SOS) listing policy. This means that when we can locate new IP space for the spammer we will list it BEFORE seeing spam samples from the spammer. It also allows escalation of the listing to cover the entire provider, and not just the source of spam. This in DNSBL terms is a collateral damage entry. The definition here is identical to the military concept.