From: "Theo Van Dinter" <[EMAIL PROTECTED]>
Don't confuse "the meta rule is executed" with "the meta rule works
as expected".
Sorry, the bad conclusion was already made and depended upon for
proper operation without cluttering the header streams or the report
fields. So the question becomes, "What is the smallest change that
can be made to SpamAssassin to effect this expected behavior?" I
believe the proposal I just made in the message I sent to the group
just before this one should meet that criterion. Even the documentation
change to clarify the issue will be mininal.
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...
I'm not sure what this has to do with anything.
If the scores are printed out in header fields the scores field can very
quickly exceed the 4k size limit. This is not a good thing.
{^_^}
