http://bugzilla.spamassassin.org/show_bug.cgi?id=3483
Summary: bayes _journal not syncing to _toks
Product: Spamassassin
Version: SVN Trunk (Latest Devel Version)
Platform: Other
OS/Version: other
Status: NEW
Severity: critical
Priority: P5
Component: spamassassin
AssignedTo: spamassassin-dev@incubator.apache.org
ReportedBy: dallase@nmgi.com
[root@mailgw bayes]# grep bayes_journal /etc/mail/spamassassin/local.cf
bayes_journal_max_size 512000
[root@mailgw bayes]# ls -la _journal
-rw------- 1 nobody nobody 1133248 Jun 7 10:25 _journal
running r20872
it looks to me like is_scan_available() is called, returns 0 because $nn < 200,
therefore it 'goto skip', which means it never gets to do
$self->opportunistic_calls();
which is where we need to get for a sync_due() to run.
So.... I have a _toks with 196 ham in it from a previous install, but the
_journal just keeps growing and never syncing newly learned 'ham' to push me
over my threshold of 200, so sync_due never runs :(
maybe moving opportunistic_calls() higher would help.. do they really need to
run at the bottom of scan() ?
i ran sa-learn --force-expire, it sync() _journal to _toks, and now i have 206
hams, and bayes is working now, and _journal is honoring its 512kb limit i
imposed on it.
so, if you come out of the bat with a brand new SA 3.0 install, you define
bayes_auto_learn 1
bayes_learn_to_journal 1
bayes_journal_max_size 512000 (doesnt really matter)
you will never have bayes. everything will learn to the _journal and it will
grow and grow and grow (unless you --force-exire of course). at least thats
how i see it, someone tell me i'm wrong :)
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
Summary: bayes _journal not syncing to _toks
Product: Spamassassin
Version: SVN Trunk (Latest Devel Version)
Platform: Other
OS/Version: other
Status: NEW
Severity: critical
Priority: P5
Component: spamassassin
AssignedTo: spamassassin-dev@incubator.apache.org
ReportedBy: dallase@nmgi.com
[root@mailgw bayes]# grep bayes_journal /etc/mail/spamassassin/local.cf
bayes_journal_max_size 512000
[root@mailgw bayes]# ls -la _journal
-rw------- 1 nobody nobody 1133248 Jun 7 10:25 _journal
running r20872
it looks to me like is_scan_available() is called, returns 0 because $nn < 200,
therefore it 'goto skip', which means it never gets to do
$self->opportunistic_calls();
which is where we need to get for a sync_due() to run.
So.... I have a _toks with 196 ham in it from a previous install, but the
_journal just keeps growing and never syncing newly learned 'ham' to push me
over my threshold of 200, so sync_due never runs :(
maybe moving opportunistic_calls() higher would help.. do they really need to
run at the bottom of scan() ?
i ran sa-learn --force-expire, it sync() _journal to _toks, and now i have 206
hams, and bayes is working now, and _journal is honoring its 512kb limit i
imposed on it.
so, if you come out of the bat with a brand new SA 3.0 install, you define
bayes_auto_learn 1
bayes_learn_to_journal 1
bayes_journal_max_size 512000 (doesnt really matter)
you will never have bayes. everything will learn to the _journal and it will
grow and grow and grow (unless you --force-exire of course). at least thats
how i see it, someone tell me i'm wrong :)
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.