Thanks Reindl, David, Martin & Joe for replying!
Reindl:
> 100 each at minimum - you only trained 23 spam samples but 1729 ham
> which is a bad balance and you would not want bayes kick in with such
> a bad database - how do you imagine a statistic analyse based on 23
> samples with a magnitude more non-spam-tokens?
It seems to actually require even more.
David:
> If you don't see any BAYES_* rule hits make sure the plugin is enabled:
>
> v320.pre:loadplugin Mail::SpamAssassin::Plugin::Bayes
>
> Run a debug lint and check for bayes output:
>
> spamassassin -D --lint 2>&1 | grep -i bayes
>
> You should see a BAYES_ in the test= line near the end.
Got it:
dbg: plugin: loading Mail::SpamAssassin::Plugin::Bayes from @INC
> Another common problem is the Bayes training is done as one user
> while spamassassin is being called by a different user. This depends on
> how/what is launching SA -- amavis-new, spamd, MailScanner, etc.
That is normally taken care of properly.
My setup is :
* postfix -> spamd (through spamc) -> dovecot on reception
* dovecot's antispam plugin -> spamd (through spamc) on mail directory
change
* sa-learn for training
All components ar invoked with the same debian-spamd user (which own
/var/lib/spamassassin -sub-directory and files).
Martin & Joe:
> There is also a strong a clue that this is designed behavior when you
> consider that Bayes has no effect on spam scoring until its has learnt
> 200 ham AND spam messages.
>
> You need to train more than 23 messages as ham first. Read the
> documentation in the SA manpages and on the wiki to make sure you meet
> every criteria for running bayes.
>
Bingo!
The spamassassin -D invocation as filtered before also popped up
something related:
dbg: bayes: not available for scanning, only 23 spam(s) in bayes DB < 200
I got no-one to blacklist, I was merely testing a custom-made 'Spam
test' message which seems to be useless (and maybe harmful in the end?).
I'll wait to be an advanced user w/ SA before attempting to
black/whitelist senders or write rules, unless events push me into doing
it ofc.
So far, all received messages have SpamAssassin headers, meaning the
delivery works and a small debug session on the antispam plugin seems to
show it reacts properly and sends commands to spamc correctly (hoping
the SA client + daemon handle/receive everything correctly).
All in all, I require more spam to trigger the bayesian filter. Only
then I will be able to assert it being running properly or not it seems.
At least it is loaded.
I thought the database (updated daily if it works) would provide it with
a kickstarted. I was probably mixing-up separate components.
Thus I sit hanging tight, hoping for the best... Thanks for your help.
---
Bernard
