http://bugzilla.spamassassin.org/show_bug.cgi?id=3214
Summary: Spamd not using per-user Bayes settings
Product: Spamassassin
Version: SVN Trunk (Latest Devel Version)
Platform: Other
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P5
Component: spamc/spamd
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
using 'spamd -d -c -m5 -H -x -q' and 'spamc -u "[EMAIL PROTECTED]"' appears to
cause
the userpref lookup to happen, but all of the bayes stuff happens for the
current user running spamd (root in this case) instead of the per user. Might be
some sort of configuration error on my part, or a bug, not sure.
Using SVN Trunk Tarball 3.0.0-r9592
CONFIG:
allow_user_rules 1
required_hits 7.0
report_safe 0
use_bayes 1
bayes_min_ham_num 0
bayes_min_spam_num 0
bayes_auto_learn 1
bayes_auto_learn_threshold_nonspam 0.1
bayes_auto_learn_threshold_spam 10.0
skip_rbl_checks 1
use_razor2 1
use_dcc 0
use_pyzor 0
razor_config /home/qscand/.razor/razor-agent.conf
ok_languages all
ok_locales all
user_scores_dsn DBI:mysql:spamassassin:localhost
user_scores_sql_username spamassassin
user_scores_sql_password [EMAIL PROTECTED]
auto_whitelist_factory Mail::SpamAssassin::SQLBasedAddrList
user_awl_dsn DBI:mysql:spamassassin:localhost
user_awl_sql_table awl
user_awl_sql_username spamassassin
user_awl_sql_password [EMAIL PROTECTED]
bayes_store_module Mail::SpamAssassin::BayesStore::SQL
bayes_sql_dsn DBI:mysql:spamassassin:localhost
bayes_sql_username spamassassin
bayes_sql_password [EMAIL PROTECTED]
Will attach a debug dump to this bug after opening.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
