The dnswl.org rules were re-enabled on 2011-12-19, and probably distributed via sa-update on 2011-12-20 (Tuesday). Because dnswl.org stopped causing false negatives in response to extreme abuse.
A new rule was added to catch return values indicating you've been blocked for abuse: RCVD_IN_DNSWL_BLOCKED To disable dnswl, you should use: score RCVD_IN_DNSWL_NONE 0 score RCVD_IN_DNSWL_LOW 0 score RCVD_IN_DNSWL_MED 0 score RCVD_IN_DNSWL_HI 0 score RCVD_IN_DNSWL_BLOCKED 0 score __RCVD_IN_DNSWL 0 That last one is really important, because without it, you'll still stop getting hits on the dnswl rules, but you'll still be sending queries to dnswl. I'm hoping that'll get fixed. DNSWL was disabled here: https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6668 Re-enabled here: https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6724 And more discussion of the subject is here: https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6728 -- "For every complex problem, there is a solution that is simple, neat, and wrong." - H. L. Mencken http://www.ChaosReigns.com
