On Nov 19, 2007, at 8:57 AM, Andrew Hearn (AAISP) wrote:
Rene Caspari wrote:
Hi,
I'm using spamassassing 3.2.3 with userspecific rules from an SQL
database:
/etc/spamassassin/local.cf:
user_scores_dsn DBI:mysql:spamassassin:localhost
[...]
bayes_store_module Mail::SpamAssassin::BayesStore::SQL
[...]
auto_whitelist_factory Mail::SpamAssassin::SQLBasedAddrList
spamc is called by procmail.
/etc/procmailrc:
:0fw
* < 256000
| /usr/bin/spamc -U /var/run/spamd.sock -u $USER
(where $USER is created by Postfix:
/usr/bin/procmail -t -m USER=${recipient} SENDER=${sender} /etc/
procmailrc)
Since I updated to 3.2.3 (Debian Volatile) I get the error message in
/var/log/mail.log:
[...] spamd: still running as root: user not specified with -u, not
found, or set to root, falling back to nobody
After this, spamassassin uses the userspecific SQL tables with the
user
"nobody" not the specific user, who is the recepient of the
scanning mail.
Do you have an idea how I can resolve this?
I think I have the same problem too, on one of our tests servers. this
is one I'm running 3.2.3 on, and using the same config from our other
3.1.7 machines which are happy with Bayes...
User preference is being used, as I can tell that as the required
score
is being set correctly from the preferences.
I've also recently seen this issue. I believe it relates to the
recent setuid changes in spamd. What I'm not sure of is if its a BUG
or just a behavior change that we need to account for. If you run
spamd in debug mode you can see it handle the passed in user and then
force the drop back to user nobody.
Michael
