Nuno Fernandes-2 wrote > Yes.. you are correct. The result is not added to the AWL database but i'm > ok with that.
Personally I think it makes no sense using AWL when you do not let it work, and do not store all scores. A better place to make the modification is at the bottom of the sub check_from_in_auto_whitelist(), in the condition "if ($delta != 0)". Store the value of the noawl tag in the loop where your current code is, but don't return from there. Let the sub parse through, and skip returning the delta score at the bottom. However, unless you manage to get this modification to the official code, you have to redo the patch after each update, so as I wrote previously, IMHO the better way to handle it, is adjusting the tag scores so that you do not need to disable AWL. You could also write a rule based on the concerned tag values, in combination with the AWL value, so that it does the same trick without the need to hack the code. Something in a way similar to this one: meta AWL_FIX (URIBL_DBL_SPA || SOMETHING_ELSE || ANOTHER_ONE) && AWL < -3 describe AWL_FIX Suppressing AWL priority AWL_FIX 1100 score AWL_FIX 5.0 It is always preferable customizing your installation through settings and rules, than hacking the code. -- View this message in context: http://spamassassin.1065346.n5.nabble.com/Disable-awl-when-some-other-rule-hit-tp108598p108678.html Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
