If this is a duplicate, just point me to the answer and I'll remove this.
I have a locally hosted email server using the ISP for the nameserver. In the email headers I get the Spam Assassin message URIBL_BLOCKED. When I google URIBL_BLOCKED the first result is https://help.directadmin.com/item.php?id=666 which says to change your resolve.conf to have nameserver 127.0.0.1, but this assumes you have a dns server running and listening on the localhost.
Moving down the Google results I find http://uribl.com/refused.shtml which has an interesting section which reads:
Low Volume Workaround? If you are low volume user, you have a few options. Possibly changing your nameservers from a public dns provider (ie opendns/google) to your local ISP may solve it. If your local ISP is also effected because they are very large (ie cox/att/comcast/etc), you may need to use your own recursive DNS solution. If your company has DNS servers, point to them for resolution. Alternatively, you could setup a caching nameserver on the loopback of the machine doing the spam checking, and point the DNS to localhost.
Can someone point me to instructions on how to do this? I've read that bind9 is a linux program that can do this but wherever I find bind instructions it's regarding how to host the dns records of my sites, not how to route my Spam Assassin URBL requests through my local nameserver.
0 Answers