20.03.2011 12:04, Matt Elson kirjutas:
Unsure if anyone else is seeing this, but the following rules in the
latest ruleset fetched around 1AM EST or so today (version 1083147 if
I'm reading the debug logs right - I don't have a copy of any previous
ones, so unknown if they are new) are creating problems in my
spamassassin install.
body __PILL_PRICE_1
m;\$?[\d\s.]{3,8}(?:/|per|each)\s?(?:pill|tablet|cap(?:sule|let));i
tflags __PILL_PRICE_1 multiple
body __PILL_PRICE_2
/(?:pill|tablet|cap(?:sule|let))s\s\$?[\d\s.]{3,8}/i
tflags __PILL_PRICE_2 multiple
body __PILL_PRICE_3
/free\s(?:pill|tablet|cap(?:sule|let))s/i
tflags __PILL_PRICE_3 multiple
Specifically, they're causing spamassassin to run in an endless loop
when the tflags line active when the rule hits. Debug just shows the
following line endlessly:
Mar 20 05:37:56.391 [6677] dbg: rules: ran one_line_body rule
__PILL_PRICE_3 ======> got hit: "Free Pills"
I don't have a full example of an email that triggers this, but I have
the body of one that will regularly trigger it here:
http://pastebin.com/iGQ2RJ6v
(And I think it's anything that would hit the rule causes the problem).
Sorry, I've not done much troubleshooting at this point to look deeper
into the issue, so it may be some quirk of my local install, but I
figured it couldn't hurt in case anyone's having a similar problem.
Problem occurred on three machines, 1 running RHEL4, 2 running RHEL5.
Looks like that means perl 5.8.5 and perl 5.8.8 respectively. I use
the Mail::SpamAssassin::Plugin::Rule2XSBody with re2c versions 0.13.2,
0.13.2, and 0.13.5.
Matt Elson
I see same here. But it only seems to happen if you compile the rules. I
have one server where I compile the rules, and this exhibited the same
problem. I have other servers where I do not compile the rules, and
these run just fine. For now I commented out the rules in 72_active.cf,
and recompiled. At least mailflow is back again :)
/Vahur
