This blacklist is no longer actively maintained, if you have a mail server that is blocking emails based on this list, please stop. I never intended this to be used to block emails anyway, as I didn’t blacklist spammers, just IP addresses that had no working abuse contact email addresses.
UPDATE: 8/8/2012: The blacklist is gone. Completely gone. If you use it, you won’t ever see anything blacklisted. If someone sent you here because your emails were blocked, this is not your problem, because no one is blocked here anymore.
There is no blacklist any more, stop using it.
Cox has decided to block all of my emails:
… while talking to mx1.west.cox.net.:
< << 554 fed1rmimpi01.cox.net IMP 22.214.171.124 is locally blacklisted
Lovely. And of course there is no way to get this block removed it would appear. Cox.net support told me to email firstname.lastname@example.org. Of course I CAN’T, since that email box doesn’t exist.
I have blocked *.cox.net in my blacklist: bl.deadbeef.com, perhaps that will help get their attention.
Update 9/25/06 20:57: Something changed, now emails are working again. From my conversation with Tier 2 support, they claim the correct resolution is to email email@example.com and firstname.lastname@example.org requesting to be removed from the blacklist. The support department also seems to be unaware of the blacklist and wants to blame your mail server.
I implemented greylisting today using the milter-greylist package for Sendmail. I built mine with the libspf2 library.
The concept is that spammers don’t implement all of SMTP, specifically they don’t retry on temporary errors. So the first time I receive an email from someone, if the SPF check fails, then I give a temporary failure error 451. Then when/if the email comes again, if at least 30 minutes have passed, I accept it. A real message will arive, just delayed, however most spammers will just give up and move on to their next victim.
This is good stuff. From 10:52AM to 4:15PM today, I received 86 spams, and this greylist stopped all but one of them, and SpamAssassin got that one.
I also during the same period received 4 real messages, which were not delayed in any way, since the senders implemented SPF correctly.