On 05/24, Kevin A. McGrail wrote: > Normally, I blame a DNS server. See pages like this for more information: > > http://www.surbl.org/faqs#dnsproxy
Yup, that could do it. Icky. Jeremy: You could manually check if you're getting the wrong DNS results by running: $ host 26.13.94.59.list.dnswl.org Host 26.13.94.59.list.dnswl.org not found: 3(NXDOMAIN) (IP address reversed, then .list.dnswl.org.) If an IP address is listed (as that one should not be), you'll see something like: $ host 40.152.71.64.list.dnswl.org 40.152.71.64.list.dnswl.org has address 127.0.6.3 > Darxus, you wrote a good wiki about using other DNS servers, etc. somewhere I > thought about but I can't find it. I did? Are you thinking of https://wiki.apache.org/spamassassin/CachingNameserver ? I didn't write it. > In general, I recommend running your own caching nameserver. Yup. -- "Safe is anywhere a hungry person can't walk in three days." - John Titor http://www.ChaosReigns.com
