why you should use efnetrbl instead of dronebl

Earlier this morning, I discovered that under it’s new administration, DroneBL has initiated a block of all Kalamazoo AT&T users without any public warning or notification.  Obviously this is unacceptable, and on StaticBox we have discontinued usage of the DroneBL service as a result.

We suggest that other networks do the same and demonstrate to the new administration that stealth blocks is entirely unacceptable and leaves the provided data untrustworthy.  The new DroneBL administrators have been notified that they should find new hosting arrangements, as I still continue to provide their infrastructure.

You can read more about EFnet RBL on their own site, they include a BOPM example configuration section.

Update: The tainted data has been purged, so I guess we’re OK now.