http://bugzilla.spamassassin.org/show_bug.cgi?id=4554
------- Additional Comments From [EMAIL PROTECTED] 2005-08-23 02:04 ------- (In reply to comment #1) > Eugene, > > 1) There's no way we can test and reproduce your problem with a cut/paste copy > of the email. Please use the Create a New Attachment link above and upload a > full copy of the email, unmodified, with full headers, for us to test > against. > > If you could also upload an exact copy of the rule, perhaps the file the rule > is > found in, that would help us to ensure we're looking at the real rule and not > an > accidental typo. I've uploaded the same email and rule as attachments. I've trimmed most headers and body content from the email as it is not spam. It hang spamassassin anyway. Just put file with rule in some directory, say 'test', and run: spamassassin --siteconfigpath test -C test -D < mail1 It will hang on the following phase: debug: running full-text regexp tests; score so far=0 > 2) [\d\w] is the same as [\w] (\d is a subset of \w). You can get rid of the > \d > without affecting the meaning/application of the rule, and if that "fixes" the > problem then that would be very useful information. No, it doesn't fixes problem. The problem can be "fixed" by removing choice '(com|br)' from the rule. > > 3) How long have you let this hang? Any time you use > [some-wide-matching-pattern-like-\w]+ in a body or full test, the use of + is > very likely to cause longgggggggg run times, with the symptoms you see. Run > times of tens of minutes have not been unknown, though unlikely with a very > short message like this. I've run it for tens of minutes. I even run it under debugperl and gdb, and gdb clearly shows that this rule and email combination causes infinite loop of calling Perl_screaminstr. Probably I should report this as a Perl bug, but the same regexp applied to the same mail in a simple script doesn't hang. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
