> Interesting, then one of the following is the cause:
0) You didn't restart the daemon after changing its config.
> 1) there's errors in your config, and SA isn't parsing local.cf at all.
> To check for this, run "spamassassin --lint". It should run quietly, if
> it complains, find and fix the offending lines.
Ahem. Always do run a lint check after any changes. Hope we can rule
this one out.
> 2) You're editing a local.cf in the wrong path. Check what the "site
> rules dir" is near the top of the debug output when you run
> "spamassassin -D --lint".
>
> 3) the offending message has multiple From: headers, and SA is
> interpreting the other one. You can try looking at the raw message
> source for this.
>
> 4) The configuration being used at delivery time is over-riding the one
> used at the command line. You can try pumping the message as a file
> through spamassassin on the command line and see what it comes up with.
> If it matches USER_IN_BLACKLIST on the command-line, but fails to match
> at delivery, something is fishy about your integration and how it
> configures SA.
--
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; }}}
