On Thu, Jul 22, 2010 at 01:27:57AM -0700, Daniel Lemke wrote:
>
>
> Henrik K wrote:
> >
> > But make sure you have SA 3.3, you should use the time_limit [2] local.cf
> > option. If you have latest SA and there are rules which "hang", you should
> > identify them (can't remember the easiest way right now) and maybe post a
> > bug.
> >
> > [1] http://www.gossamer-threads.com/lists/spamassassin/users/151763
> > [2]
> > http://spamassassin.apache.org/full/3.3.x/doc/Mail_SpamAssassin_Conf.html
> >
> >
> >
>
>
> Hmm, is it possible that time_limit effectively doesn't stop SpamAssassin
> from parsing the regexes? I set it to 5 seconds for testing purposes and fed
> it with a text mail. Scantime was over a minute and no time_limit_exceeded
> reported in the report.
Yep seems so..
"Note that $SIG{ALRM} is used to provide the timeout, so this will not
interrupt out-of-control regular expression matches."
Works even less since most of the rules are priority 0 and there is one hard
check per priority..
PS. Maybe newer Perl version could help a little?
