>> given that install unbound as local resolver takes 2 minutes it's even not >> worth to argue on that topic and a spamfilter without RBL's and URIBL's is >> just nonsense
>I have installed a caching DNS server before (albeit probably about 15 >years ago). But it just shouldn't be necessary. It can be necessary if you have enough mail volume. >By "librarified" I mean the DNS "server" is just a code context that >can be constructed with it's own config precisely and only as needed >by the software that will be querying it (possibly temporarily if it's >just client-only activity like a barrage of DNS queries fired in >reaction to an email that fails other spam tests). It should not be >necessary to change the resolver configuration or behavior of the >entire system and everything running on it if only one component in >the system needs this special feature (in this case a query limit and >private cache). That is just bad programming philosophy and it the >source of a lot of bad behavior in software (and DNS is a very good >example of this actually). You obviously don't understand how DNS works in relation to RBLs. We are giving you solid advice based on real experiences where we ran into problems and worked around them. Just try to enable RBLs and see how it works for you. >Not everyone is running a dedicated mail server. My server is an >everything-server running on a hosted VPS that only has a few "users" >that get significant amounts of email. I'm not sure I want another >daemon that can break or take up clock cycles and memory on a system >processing 10 spams / hour (of which the DNSBL service might catch >2?). At least not yet, but I suppose I could change my mind. At the >moment not that many spams are getting through. >Mike You asked for help, we provided it. It's fine if you ignore the advice, but it's good advice if you want to take your mail filtering to the next level in the future.
