On Thu, 2010-01-28 at 12:39 -0500, Alex wrote:
> > The rules in /usr/share/spamassassin are the original rules from the
> > install. If /var/lib/spamassassin/3.002.005 exists, those rules will be
> > used instead. You can verify which rules are being used by running this
> > command:
>
> Is this order documented anywhere?
man spamassassin
See the Configuration Files section there, pay special attention to the
part that reads "Default configuration data is loaded from the *first*
existing directory in" and the following list. Emphasis added.
Also most likely documented in quite a few other places, including the
SA wiki. I'm aiming for the low hanging fruit here... :)
> When I had this 20XX date problem, it was because
> /usr/share/spamassassin was still being consulted, despite
> /var/lib/spamassassin having the latest rules.
Seriously doubt that. Unless you either didn't restart spamd or a
similar daemon after sa-update, or didn't run sa-update after the rule
has been fixed.
--
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; }}}
