https://issues.apache.org/SpamAssassin/show_bug.cgi?id=4900
--- Comment #18 from Matt Kettler <[email protected]> 2010-04-18 22:21:05 EDT --- > 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. 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. To be honest, this particular concept actually makes me oppose making any AWL extension that has a persistent effect. If it's really persistent, it belongs in the configuration file, where they can be easily seen, no? Long-lasting score hacks muddy the waters of what the AWL is doing, and make it difficult to see that "oh yeah, I did an over-ride for that" unless you go dumping though the AWL database. We may end up getting lots of "why is my AWL being crazy" complaints if it gets rolled into the AWL. I'd consider the mod if it got reported as a separate rule (AWL_OVERRIDE or some such), but I'm really leaning towards opposing it because the nature of the AWL is intended to be transitory, and the config files are intended to be persistent. Use each for their intended purposes. -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
