https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6633
John Hardin <jhar...@impsec.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jhar...@impsec.org
--- Comment #2 from John Hardin <jhar...@impsec.org> 2011-07-12 15:25:57 UTC ---
I find it really difficult to believe that Bayes would cause scanning timeouts
absent other factors. Can you provide debugging traces that show the timeout
and include whatever indicators lead you to believe that the number of words is
the causative factor? A sample of a spam that SA timed out on would be helpful.
Typically when things start timing out we first recommend looking at memory and
number of child processes, as the most common cause for timeouts is overloading
available memory and hitting swap. What are the resources available on the
computer that's hosting SA?
There's also the possibility of local rules that have runaway backtracking
caused by certain spam content.
I'd strongly suggest taking this to the users list and hashing out whether or
not it really is the number of words in the messages that's causing the
problem.
--
Configure bugmail:
https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
