> The problem is, Daryl...there's a handful of users that get a certain type
> of spam that DOESN'T process in the usual timeframe. In fact, even on a
> spamassassin restart, those messages come right back in, and eat a process
> space and NEVER finish. Presumably they also consume CPU time and
> whatever else.
If you have spam that isn't finishing then I can only think of two possible
reasons:
1) The spam is bloody huge and you don't have the usual 250KB limit on
message size passed to SA.
2) You have a rule (or even more than one) that has a problem, and is
getting hung up by some pattern in the mails that never finish. This can
pretty easily happen if you have a rule with a couple of .* terms in it
separated by other junk. This has even happened a couple times in the past
to SARE rules that we thought were carefully written, but eventually hit a
pathlogical case of one sort or another.
At the moment I'm betting that you have a bad rule, possibly of local
origin. Get that fixed and you should stop hitting these bottlenecks, at
least ones caused by this problem.
Loren
