I understand what you're saying -- whitelists shouldn't always override blacklists. But if I tried to change this, how would it work? Perhaps whitelisting a specific address (e.g. [email protected]) would override a domain blacklist (e.g. @domain.com) while blacklisting a specific address would override a domain whitelist? But what about all the other blacklist/whitelist options? Do DNS RBLs override DNS RHSWLs? Do rDNS blacklists override IP whitelists? Do entries in configuration directories override entries from the global configuration file? Should the order of priorities itself be configurable?
Overall this looks like a troubleshooting nightmare to me -- an administrator would never be able to understand whether a whitelist had priority over a blacklist without rereading the documentation (and possibly testing it to be sure). I understand the problem you're facing, but I think making blacklists override whitelists some of the time would cause a lot more problems than it would solve. -- Sam Clippinger On Jul 29, 2012, at 5:04 AM, Lutz Petersen wrote: > > Hi, > > I've some trouble with spamdykes recipient blacklist option. Let me > give you an example: > > Recipients domain is @domain.tld > > Now theres flooding in senseless mails for <[email protected]> and > I made an blacklist entry for this recipient. > > This works fine for a lot of cases. But, for example, all mails from > the spamfree yahoo community (thats a joke if you don't understand..) > will get through. This is because any kind of whitelist match overwrite > any kind of blacklist match within the spamdyke logic. And well known > mailservers like that one from yahoo naturally are within our own dns > whitelist (to prevent blocking) or in others like dnswl.org etc. > > I don't see the sense why an explicit 'blacklist recipient' entry > should ever be overwritten from any whitelisting. The only solution > I found for this special case (beware, this single case made some > 10000 senseless emails every day) was to add this single recipient > address not in spamdyke but in qmail's badmailfrom file. > > Lutz Petersen > > _______________________________________________ > spamdyke-users mailing list > [email protected] > http://www.spamdyke.org/mailman/listinfo/spamdyke-users _______________________________________________ spamdyke-users mailing list [email protected] http://www.spamdyke.org/mailman/listinfo/spamdyke-users
