Merijn van den Kroonenberg wrote on 10/06/16 10:17 PM: > What does this mean, can still a single operation take more than this > time_limit?
There is a fundamental difficulty in perl that the built-in timer alarm facility cannot always interrupt the built-in regular expression matching facility. That means there is not a good way of protecting against a rule pattern that can take a very long time to process certain input being given that input. There is some effort to do that with the time_limit setting and spawning of individual child processes in spamd that can be individually killed if one of them gets hung up, but that only goes so far. More technical discussion of how to better deal with this probably would be better in the dev mailing list. There have been a number of bug reports having to do with some "toxic" email bogging down SpamAssassin which were tracked down to some use of, for example, .* in a rule pattern. It can be tricky to fix a pattern to keep this from happening. When you write your own rules for local use you are more likely to run into this problem because you probably have less experience in writing patterns to avoid it and don't run your rules through the many test cases of our mass check system. Sidney
