https://issues.apache.org/SpamAssassin/show_bug.cgi?id=4900
--- Comment #23 from Matt Kettler <[email protected]> 2010-04-23 06:03:26 EDT --- First: Even if you are using a site-wide configuration there is still a user_prefs. You can use that user_prefs without restarting spamd. This is because a site-wide configuration is nothing more than a setup where SA always runs as the same user. That user still has a home directory in /etc/passwd, and SA will still try to go there and load user_prefs. Claiming that local.cf and spamd restart is the only option for a site-wide configuration is bogus. I will grant that editing a file is less-than optimal is valid, but there are ways where you don't have to restart spamd. Your custom shell script could be modified to a small perl or python script to manage a user_prefs file. This would take a bit of work, but it is hack-free. Second: Putting black/whitelist data into a config file may be a "hack" to you, but putting it into the AWL database is an extraordinarily egregious hack to me. The AWL is a dynamic score averager, it is not a blacklist or whitelist, and it is not static in nature. Persistent score settings are fundamentally counter to the nature of what the AWL is, because it is fundamentally dynamic not static. Although adding this static data would seem to fit with the AWL's ill-chosen name (auto white list), it does not fit with the reality of what the AWL actually is. Adding static data to it is going to involve a really ugly duct-tape and kludging wire hack. This is my primary reason for resisting this change. It may be convenient from the perspective of the user interface, but the insides of making it happen are going to be really horrible and ugly. -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
