On Fri, 2013-11-08 at 16:09 -0200, Sergio Durigan Junior wrote:
> #> spamc -c < spam.file
> 0.0/5.0
> #> spamc -L spam < spam.file
> (successful message saying that the spam was learned)
> #> spamc -c < spam.file
> 0.0/5.0
You mentioned that's a fresh install, actually not even in production
yet. The Bayes sub-system requires some training (minimum of 200 ham and
spam each) by default, before Bayes rules kick in for scanning.
Instead of -c check only, use the -R option to print the report. You'll
notice there is no BAYES_xx rule (yet).
> I have already updated my Bayesian database, restarted the spamd
I'm curious -- what does updating your Bayes db mean?
> service, etc. I was expecting that I'd get a high rate after feeding
> the spam to SpamAssassin, but that's not happening. Any suggestions?
In addition to required initial training:
The Bayesian classifier works on a per-token (think: word) basis. Thus,
depending on the tokens in the message and existing ones in the db, the
impact of learning can vary quite a lot -- from hardly noticeable to
clear detection.
--
char *t="\10pse\0r\0dtu\0.@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}
