On Wed, 2011-01-05 at 16:29 -0800, Frank Chan wrote:
> I noticed recently (within the past two months) I'm getting this
> error message from spamassassin. Here is line from the maillog:
>
> Jan 5 15:07:40 s1 spamd[21160]: check: exceeded time limit in
> Mail::SpamAssassin::Plugin::Check::_rawbody_tests_0, skipping further
> tests
Priority 0, the default. Do you by chance have custom rules, that might
in some pathetic edge cases result in lots of backtracking and burning
CPU resources galore?
Did you try temporarily removing all custom rules? Any pattern, as to
when this happens? Some specific messages? Do you have a sample
triggering this?
> I have set spamd --timeout-child=300 so should I raise it to about
> 600 but will there be consequences like spammer overloading the
> server to lockup all spamd processes or other problems this can cause.
A 5 minute timeout should be plenty, and even with CPU intensive checks
like rawbody is, more than ever should be necessary. Otherwise, you
won't be able to process more than number-of-cores messages per 5
minutes interval...
--
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; }}}
