Anthony Cartmell-2 wrote > The caching aspect isn't particularly relevant. > > The problem is that your ISP's name server will be querying the URIBL > server on behalf of perhaps thousands of SpamAssassin instances on other > machines. So it's blocked because it's making too many queries from a > single IP address.
Yep, thank you, already figured this out. My problem was that I was not sure how exactly DNS works, and by studying dnsmasq configuration I incorrectly assumed that a dns server is always supposed to have an upstream server. Apparently this is the case for dnsmasq but not the case in general. So now with djbdns setup that I have in place that perform recursive queries starting from the root servers this all makes sense. Thank you again. -- View this message in context: http://spamassassin.1065346.n5.nabble.com/Why-do-I-get-both-URIBL-DBL-SPAM-and-URIBL-BLOCKED-tp109457p109466.html Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
