***********************************************
ACTION REQUIRED: If you wish to continue to query the DNS{W,B}Ls run by
Validity (nee "Return Path") you MUST set non-zero scores to the relevant rules
in your local.cf file, effective with the distribution of today's rule changes
(i.e. Wednesday-ish) including revision r1925516.
***********************************************
After reviewing Bug 8278
(https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8278,) the conversations
here, what we have documented as policy, and feedback from masscheck
contributors, I have set all 3 Validity-related rule scores to 0 and commented
their "BLOCKED" rules, assuring no more queries from anyone who does not
affirmatively wish to do so.
This is consistent with how we handled a similar situation with MAPS: we still
publish the rules but they are scored at zero because they require paid
accounts now (and have for MANY years)
The reason that I changed my mind since my last post about this is simply that
I re-examined the many facts available, prompted by a note on the bug and by 2
posts to the RuleQA list by contributors, which led me to look at RuleQA. That
got me to understand 2 harms from leaving the rules scored:
1. It makes the "net" masscheck results randomly incoherent, in a way that is
sure to confuse/mislead users who try to make sense of the Validity results in
RuleQA.
2. It annoys our masscheck contributors, who we absolutely do not want to annoy.
I also realized that we didn't need to make the binary choice to include or
exclude the rules, but could just do as we did with MAPS, leaving the rules
extant but scored to zero so that they do not get tested.
--
Bill Cole
[email protected] or [email protected]
(AKA @grumpybozo and many *@billmail.scconsult.com addresses)
Not Currently Available For Hire
