https://issues.apache.org/SpamAssassin/show_bug.cgi?id=4900
--- Comment #20 from Matt Kettler <[email protected]> 2010-04-19 06:46:44 EDT --- (In reply to comment #19) > (In reply to comment #18) > > > I don't understand how it can be a good idea to keep variable data in a > > > config > > > file. > > > > Wait... This whole bug is about making AWL over-rides persistent. So is this > > data variable, or persistent? Pick one. > > Are you trying to be clever? If by "clever" you mean rude, no. I'm merely pointing out we've got a contradiction here that needs resolution. Is this data in question persistent, or dynamic in nature? How persistent or how dynamic is it? I'm being serious, because we can't argue both sides. > > The list of mail addresses to be blacklisted/whitelisted is of course variable > in that more addresses could be added to it at any time. > Every address put in that list should stay there until the user removes it. > > > If you want the AWL mods to be short-lived, the existing mechanism works. > > > > If they need to be persistent, then a config-file mod (user_prefs, etc) > > shouldn't be a problem. > > Do you really think that everyday users of a spamfilter want to edit their > configuration file and restart the service for every address they encounter > that they want to put in a blacklist or whitelist? Do you really think these same users are prepared to go dumping though the cryptic AWL database to find the addresses they previously whitelisted or blacklisted to remove them? > > I think this is completely silly. > A config file holds data that makes this installation different from the one > nextdoor. Things like a local domain name, filesystem paths, policies, etc. > But not a list of addresses that is maintained daily. If you are modifying your black or whitelist daily, something is *severely* wrong with your SpamAssassin install. I've made maybe 20 such entries in 5 years of running a server with site-wide configuration for 100 users. This may be a bit on the abnormally low side, but long-term black and white lists should be a measure of absolute last resort, not daily maintenance. -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
