http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5611
Summary: Running spamd with -u and without -x no longer reads
user prefs
Product: Spamassassin
Version: 3.2.2
Platform: Other
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P5
Component: spamc/spamd
AssignedTo: [email protected]
ReportedBy: [EMAIL PROTECTED]
My system has a setup where:
* spamd runs as a dedicated spamd user, which is in a spamd group
* every user has their own configuration in $HOME/.spamassassin
* configurations are 660 user:spamd, so that both the user and spamd can
read/write them, but none of the other local users can
This configuration stopped working in 3.2.2; instead of reading the preferences
of the user who invoked spamc, SpamAssassin would read the spamd user's
(non-existent) preferences.
I think this is a side effect of the patch installed from bug 5522.
I've fixed this problem with the attached patch. This is sloppy and so I would
imagine this is something you won't want to install directly, but I think the
end result has to be that handle_user_set_user_prefs always loads the
preferences of the user who called spamc, rather than the user spamd is running
as (which it currently does).
I think the check for $opt{'user-config'} around the handle_user_set_user_prefs
call in handle_user_setuid_basic should make sure the -x case still works, but I
haven't tested that.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.