On Wed, 2010-03-31 at 19:15 +1100, Phill Edwards wrote: > I have just found out why most of my emails have been getting tagged > as spam this year. It's because of a bug in a rule which causes this > hit to happen when it shouldn't: "FH_DATE_PAST_20XX The date is > grossly in the future". The actual file at fault is 72_active.cf which > is a spamassassin rule file and it can be fixed by getting the new > file via sa-update. > > But I don't understand how to use sa-update. I've run it and I can see > all the new rule files in /var/lib/spamassassin/3.002005. However, I > think my rules run off the files in /usr/share/spamassassin/. The wiki
man spamassassin Pay special attention to the section Configuration Files. sa-update is doing the right thing, and spamassassin will use the update dir instead of the base stock rules. You merely need to restart spamd, or whatever else you are using. > at http://wiki.apache.org/spamassassin/RuleUpdates#Using_sa-update > says NOT to use the "--updatedir" parameter to put updates in > /usr/share/spamassassin. So how exactly do you get the new rule files > into /usr/share/spamassassin so they start working? Do you just copy > them across manually, or is there a way of getting sa-update to do it > automatically? Pretty much the same answer as above. Do not move, copy or otherwise harm those files. :) sa-update knows, where spamassassin expects the rules. guenther -- char *t="\10pse\0r\0dtu...@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; }}}
