http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4445
------- Additional Comments From [EMAIL PROTECTED] 2005-12-13 02:45 -------
Can't. Loren and I need different rules. There are similar rules in the various
configuration files within the /etc/mail/spamassassin directory. They do not
trigger the problem. I've taken out the "offending" rules for testing and the
problem went away. I put the rules back because they were effective. I suppose
this test is as effective as the test you wanted. The rules are more or less
adapted clones of existing SARE rules at the time.
Typical rules are or have been:
full JD_INVALID_ZIP /UEsFBgAAAAAAAAAAAAAAAAAAAAAAAA\=\=/s
describe JD_INVALID_ZIP Invalid - empty - zip file.
score JD_INVALID_ZIP 5
full JD_TABLES /table cellpadding\=\"0\" cellspacing=\"0\"border=\"0\"/i
describe JD_TABLES table cellpading=0 and so forth
score JD_TABLES 2.50
===8<---
There should be a way to get the actual rule that caused the error dumped out
to a log without dumping everything.
I've folded in the 3.0.5 changes. So if 3.0.5 "should have this fixed" it
probably is fixed. I'll reenable by trap to check for it. But that will not
tell us the rule that actually failed. I suspect that migh tbe important.
I have rules for "rawbody" and "full" that trigger two of the places the error
can hit. I believe there are three places in the code that use this kind of
evalstr.
Loren and I tried to hack on 3.0.4 and get the failed evalstr to at least print
out. Neither of us is enough of a perl hacker to achieve that goal.
{^_^}
{^_^}
{^_^}
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
