http://bugzilla.spamassassin.org/show_bug.cgi?id=3503
Summary: local.cf not reread, forced to use @GLOBAL for
everything...
Product: Spamassassin
Version: SVN Trunk (Latest Devel Version)
Platform: Other
OS/Version: other
Status: NEW
Severity: major
Priority: P5
Component: spamc/spamd
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
Just upgraded from a snapshot from a few weeks ago, and noticed the following
symptom.
In local.cf I have report_safe 0. In per-user SQL preferences I sometimes have
'report_safe 1'.
The behavior is that once a user with report_safe 1 has been processed, all
users get report_safe 1. It never re-reads local.cf or re-processes those
preferences. It did not appear to do this with other parameters, such as
whitelist/blacklist.
Reason I noticed is that all of our users started getting report_safe 1 behavior
when only a few (out of several thousand) had it set that way.
I didn't see any mention of this change in behavior in the docs. For now I've
worked around by adding report_safe 0 to @GLOBAL, but I'm concerned that other
prefs may be behaving the same way. Per-users prefs having non-temporary effect
on the spamd server isn't a good thing.
FYI - I had kept things in local.cf as a performance boost for local params that
change infrequently... Why transfer the extra rows from the database every time
when they can be cached in memory once.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
