On Tue, 2011-02-15 at 14:37 +0100, J4K wrote:
> Also, I thought that one only had to run spamassassin --lint once. I
> did a month ago. Afterwards, I thought that only sa-compile had to be
> run.
It's a syntax check, reporting errors with your configuration and rules.
The lint check is not necessary to be run for sa-compile, even less so
once only. It should, however, be run *every* time you change either
configuration or rules.
> Its pretty moot any way, because now after running spamassassin -lint,
> sa-compile still fails with the same error.
Yes. Because lint check merely reports the issues, so you fix it.
--
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; }}}
