TIMING [total 846599 ms] ???

[Matthias Keller <li...@matthias-keller.ch>]

Hi

I've just noticed two messages tonight which for some reason kept up my 
SpamAssassin 2.64 for nearly 15 and 7 Minutes respectively!!?
My log shows for those two messages:

Nov 26 19:30:40 mindblow amavisd[3846]: (03846-09) TIMING [total 846599 
ms] - SMTP LHLO: 5 (0%), SMTP pre-MAIL: 3 (0%), SMTP p
re-DATA-flush: 8 (0%), SMTP DATA: 79 (0%), body hash: 3 (0%), 
mime_decode: 47 (0%), get-file-type: 29 (0%), decompose_part: 3
(0%), parts: 0 (0%), AV-scan-1: 852 (0%), SA msg read: 8 (0%), SA parse: 
7 (0%), SA check: 845092 (100%), write-header: 16 (0%
), fwd-bsmtp: 3 (0%), fwd-connect: 147 (0%), fwd-mail-from: 38 (0%), 
fwd-rcpt-to: 8 (0%), write-header: 16 (0%), fwd-data: 90
(0%), fwd-data-end: 123 (0%), fwd-rundown: 4 (0%), unlink-1-files: 19 
(0%), rundown: 1 (0%)

Nov 26 19:37:20 mindblow amavisd[3846]: (03846-09-2) TIMING [total 
400053 ms] - SMTP pre-DATA-flush: 8 (0%), SMTP DATA: 400044
 (100%), unlink-0-files: 1 (0%), rundown: 1 (0%)

The first spent all the sime on SA - while it seems the second 
apparently got some SMTP timeout... (might be related to the first one?)
The first message is a quite big Spammail, containing of only about 4 
Lines of body but being of size 28k
It's a HTML Mail with lots of bayes poisoning and opening and closing 
tags...
Might those VERY long lines be a Problem for SA?
When using -D on spamassassin to check it directly, it gets with normal 
speed until it reaches this:

debug: running raw-body-text per-line regexp tests; score so far=8.789
There it stays for ages, using 100% cpu

Any known problem? I'd be happy to provide the mail in question to 
anyone interested.

Thanks a lot!

Matt