From: "Daryl C. W. O'Shea" <[EMAIL PROTECTED]>
Bret Miller wrote:
So what we're saying here is that if you create a META rule on a
disabled (scored 0) rule, the META rule doesn't work?
Disabled means disabled. Disabled rules are never run.
Quoting the relevant score config info from M:SA:Conf POD:
score SYMBOLIC_TEST_NAME n.nn [ n.nn n.nn n.nn ]
Setting a ruleâs score to 0 will disable that rule from running.
Note that test names which begin with â__â are indirect rules used to compose
meta-match rules and can also act as prerequisites to
other rules. They are not scored or listed in the âtests hitâ reports, but
assigning a score of 0 to an indirect rule will disable
it from running.
Didn't work before either?
There has been *zero* functionality change.
Or still works but generates an info debug message? Guess I
should go dig out the rest of this converation and go read the bug
discussion...
Having to score every component of a META rule seems like a bad thing...
My MTA integration only allows for 4K of headers to add and I'm already
exceeding it fairly often. Adding more insignificant rules to the list
will just make it that much worse...
If you disable a rule it doesn't run. Period. When your eval is run it'll use a false
result in place of a disabled rule. Thus is the rule is a required part of the meta
(it's ANDed) then the meta will never fire. If it's an optional part of the meta (it's
ORed) then the meta will fire if it goes on to evaluate true.
That is a bad thing. And it also seems to be different from the original
version of SA I started with which supported META. (I started back with
2.20 something.) The wording back then suggested you could write a META
rule with components scored zero so that they would not report but the
META would still work. That behavior is depended upon for some of the
SARE rule sets, it appears.
Could it be possible to enhance SpamAssassin with an artificial score,
"META". Internally that would be interpreted as something like 0.0001
so that the rule would fire. Then make a second change so that any rule
with a score equal to or under META, 0.0001, does not print out in the
reports individually?
If so I can (grit my teeth and) file a bugzilla request for the change.
This should be a minimal change that would create the desired and user
expected behavior.
{^_^}
