http://bugzilla.spamassassin.org/show_bug.cgi?id=3214
------- Additional Comments From [EMAIL PROTECTED] 2004-03-25 14:48 -------
Subject: Re: Spamd not using per-user Bayes settings
On Thu, Mar 25, 2004 at 02:28:26PM -0800, [EMAIL PROTECTED] wrote:
>
> ------- Additional Comments From [EMAIL PROTECTED] 2004-03-25 14:28 -------
> Got the per-user bayes stuff to start showing up in the database by hacking
> the
> handle_user_sql function in spamd.
>
> sub handle_user_sql {
> my ($username) = @_;
> unless($spamtest->load_scoreonly_sql(@_)) {
> $spamtest->signal_user_changed ({ username => $username,
> user_dir => "" });
> return 0;
> }
> $spamtest->signal_user_changed ({ username => $username,
> user_dir => "" });
> return 1;
> }
>
Yeah, but the real question is why was it not already signaling that
the user had changed?
Anyone know?
> This however, brings up a bigger issue, when combined with Auto-Learn, in that
> it will auto-learn and plug stuff into the database for every incoming email
> when used from something like qmail-scanner on the front end system-wide. So
> even non-existent accounts get plugged into the bayes database. There should
> probably be some check with either a vpopmail lookup, or a system lookup to
> verify an account before logging bayes stuff maybe?
Hmmm...this is an interesting problem, can you open up another bug so
we can track it separately.
> Also, there's currently no way I can see to get ham into the bayes database
> on a
> per user basis. It looks like to fully make use of the bayes database stuff a
> flag is needed on sa-learn to give it a user.
Yeah, I think there is a bug somewhere, you can cheat by setting
bayes_sql_override_username to the username you wish to train for.
Michael
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
