On Mon, 2011-03-21 at 07:45 -0500, Dan Grossman wrote: > > > Hmm ... my problem is that I can't get the bug to go away. I've > > > commented out the offending lines in the ruleset download location, and > > > yet the problem still happens.
> As far as I am aware, I do not use sa-compile. My /etc/cron.daily > sa-update.sh script just runs sa-update. > > Also, none of my config files in /etc/mail/spamassassin refer to > compiled rules. All those lines are commented out: Are you sure you are suffering from this issue, then? What exactly did you comment out, and where? Anyway, does the easier trick mentioned in bug 6558 [1] comment 3 fix it? It really should. [1] https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6558 > Because I have a small number of users, I run SA directly from > procmail; SA is launched separately for each new piece of mail that > arrives. Even with a small number of users, I strongly suggest to use spamc/d instead of a plain spamassassin call from procmail. -- 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; }}}
