When SA parses a message, it needs to know when the headers end and the body begins. In the current 3.0 code, we assume that the header ends at either a blank line (normal) or when we see a MIME boundary. The problem is that we parse the Content-Type header so we can figure out what the boundary string is, and if SA receives an extremely long Content-Type header (especially one with tons of whitespace folding/continuation) that doesn't have a boundary in it (or it's at the end), parsing it over and over causes lots of wasted CPU time.
This issue should also affect RHEL2.1 and RHEL3
http://people.redhat.com/wtogami/temp/spamassassin/el4/ Test package, waiting for decision about embargo lift on details
I was wrong, this issue does not affect RHEL2.1 or RHEL3
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2005-498.html