http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5041
------- Additional Comments From [EMAIL PROTECTED] 2006-08-17 20:29 ------- Mark, some comments in response to your comment 19 : The example is bigger than our recommended maximum size. Also, the example is something that should be whitelisted. In fact, it's probbly a good idea to have local mail from cron jobs not run through SpamAssassin at all. Of course that doesn't change the fact that this is an example of a message that takes 200 seconds to process, which means it could provide insight on what needs to be done to prevent, say, 100 second messages that can't be filtered out so easily. It does demonstrate that the problem is not restricted to BASE64 or UUE encoding and so we cannot simply try to detect those to fix it. That's good in a way, because as has been pointed out we can't easily filter for UUE encoding and this way we won't get frustrated trying to do that. Running spamassassin with -D and looking at the time stamps does not show which rules are taking the time. The only rules that show up there are the ones that hit. You should use profiling as Theo described in comment 17 Some of this could be helped by the xs work Justin is doing. That doesn't help Bayes tokenizing. Does it make sense to use an xs for that? Can that be sped up in pure perl? Another approach is Justin's comment 15 on looking at only the first n lines of non-HTML text, which is what I'm leaning towards now. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
