RFC-i blocklist shutting down

The RFC-ignorant blocklist announced on 9/15 that it will be shutting down service.
I commend Derek and his team for how they’re handling the shut down. All too many blocklists have been shut down due to owner burnout with disastrous consequences. Most of these lists did things like listing the whole world or just pulling domains out of the roots. Both types of shutdown methods cause problems for unrelated entities. In one case, a major DNS provider was dealing with what looked like a DOS attack after one blocklist shut down.
I’ve certainly had my differences of opinion with the folks behind RFC-i over the years, but I commend them for announcing the shut down ahead of time and gracefully shutting down RFC-i.
 

Ask Word to the Wise
Thanks for your questions!

Related Posts

Comcast changes

I updated the Wiki a few weeks ago when I heard, but don’t think I posted anything here. Comcast has changed their delisting form page to http://postmaster.comcast.net/block-removal-request.html. The old form is currently non-functional. You can fill it in, but it’s unconnected to anything on the back end and it won’t result in an IP being delisted from the various Comcast blocklists.
My understanding is that the old form may come back to life at some point, but it’s much safer to use the new form and the new Comcast Postmaster Site.

Read More

Changes at Comcast Postmaster

Two changes at the Comcast Postmaster page that I think are worthy of mentioning.

Read More

I'm on a blocklist! HELP!

Recently, an abuse desk rep asked what to do when customers were complaining about being assigned an IP address located on a blocklist. Because not every blocklist actually affects mail delivery it’s helpful to identify if the listing is causing a problem before diving in and trying to resolve the issue.

Read More