Looks OK, but the problem is that the new score won't be added to the AWL database. So for example if AWL tells the average score is 1.0, your RBL tells it ought to be 10.0, AWL would normally reflect it, the average score for the given email/IP combination would increase, and the next time AWL could catch the spammer even if the RBL failed to do it (for example when using another dynamic IP on the same block, or when the RBL was offline).
If you fear that AWL would override the score, just set the score for your RBL sufficiently high, and it won't happen. You could also try the new TxRep replacement of AWL - it uses a more sophisticated method, learns quicker, and avoids better false results. Unlike AWL, it can be also trained on past spam and relearned on new one, and it can also use the auto-learn feature, so if your high priority RBL triggers the auto-learn process, the sender's reputation will be adjusted accordingly (much stronger than just by adding the new score to the total). -- View this message in context: http://spamassassin.1065346.n5.nabble.com/Disable-awl-when-some-other-rule-hit-tp108598p108644.html Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
