Now stop using dsbl.org blacklisting: it’s offline

It seems a lot of Blacklist filters still use the old DSBL DNS Blacklist, but it's been dead for few years already. Since March 2009, to be exact. However, something changed in the last 24 hours that actually made them go offline.

The result is that any system still using that blacklist sends out bounce messages such as this.

The following recipient(s) cannot be reached: xxx
Service unavailable; Client host [x.x.x.x] blocked using list.dsbl.org

If you still have legacy systems running that use the list.dsbl.org blacklist, you may want to remove any references to the DSBL in your configs and stop using that blacklist.

Hi! This is a blog where I write down solutions to some of the problems I've faced when working as a sysadmin/dev. I hope you find the information shown here useful to you. Please use the comments on this blog to give feedback about the content!. I'm @mattiasgeniar on Twitter.

Tagged with:
Posted in Devops, linux

Leave a Reply

Your email address will not be published. Required fields are marked *

*

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>