Spam slipping through (was: Issues with sa-update - seems to be running but not really updating)

[Karsten Bräckelmann <gu...@rudersport.de>]

On Wed, 2009-04-22 at 08:25 -0600, Dan Roberts wrote:
> I am running Spamassassin Version 3.2.4 with Perl Version 5.8.8 on a  
> CentOS Linux 5.2 system.
> 
> As FAQ postings and other notes appeared to suggest running sa-update  
> daily, I set up a cron job to do that.   Though it has updated in the  
> past, it seems most of the time to find nothing to update, yet the  
> volume of spam getting through is definitely increasing.

Not for me... ;)

Seriously, this hardly can be "fixed" with an sa-update run, but
indicates there is much room for improvement of your local install, or
probably even a mis-configuration.

As always, we can't give any advice how to improve spam detection,
unless you provide samples. Well, other than re-iterating [1] over and
over again what's been posted here. It's in the archives. Yes, lurking
on and reading lists often yields hints before one even has the problem.

Please either use your own web-space or a pastebin to upload full, raw
samples including all headers. Provide a link, don't post spam samples
on-list.

  guenther


[1] Some of them:  Enable network tests, train Bayes. Use third-party
    rules and plugins, like iXhash, SOUGHT and 90_2tld for URIBL
    results. The latter shows quite some impact recently.

-- 
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; }}}