Believe me, there are good reasons to use whitelists within spamdyke on bigger installations. Not because I'ld like yahuh, hotfail or so. In the last time I see a trend that more and more spam seems to be send out via mailservers from well known carriers/isps. The botnet driven sites mainly go directly out and can relative easily be filtered (rbls, spamdyke options, simscan-score-points, ..). But those that comes in from huge mailservers you can't really block; if doing so you would block 99,9% of ham mails coming in from there too.
In the past weeks we had a lot of success in blocking spam from botnets - some of them can be simple identified by sender adress etc. and with a combination of dns white-/blacklists _and_ rules within spamdyke nearly all of these shit was blocked, very nice. But - as I said - one will not block normal mailservers, and this fine combinated rules worked fine for botnet-driven-pcs, but all thos mail that came in via normal mailservers weren't blocked because of the general whitelist behaviour in spamdyke. I understand sam, the rules are consistent and one should not confuse the admin. So, what's about a additional rule named e.g. [email protected] or something like that? _______________________________________________ spamdyke-users mailing list [email protected] http://www.spamdyke.org/mailman/listinfo/spamdyke-users
