http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5606
------- Additional Comments From [EMAIL PROTECTED] 2007-08-16 21:00 ------- I can confirm this in branch/3.2 and in trunk. The problem appears to be that spamd reads ~/.spamassassin/user_prefs when it starts up even if the -x option is telling it not to read per-user config files for each message. SATest.pm uses -x with spamd and -p with spamassassin to prevent contaminating the tests with user's actual preference file. Unfortunately, that isn't what spamd -x means. We either need to decide that spamd should not read the user_prefs file of the userid it is started up under, or else should add an option that does the same thing as spamassassin -p. I think that the former makes more sense, since spamd is already reading the various *.pre files for system configuration, and each child can read the appropriate user's user_prefs. It is confusing to have a base user_prefs file and then read a per-user user_prefs file on top of it. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
