I am playing with the Short Circuit plugin to speed up scanning (by skipping Network Tests on obviously good emails) and wanted to be able to query the AWL as part of this as I don't want to Short Circuit on BAYES_00 alone.
i.e. Short Circuit as HAM if both BAYES_00 & AWL fire. I tried this: priority USER_IN_WHITELIST -1000 priority ALL_TRUSTED -950 priority BAYES_00 -400 shortcircuit USER_IN_WHITELIST on shortcircuit ALL_TRUSTED on # Add a high priority rule to check if the sender is in the AWL header __MY_AWL eval:check_from_in_auto_whitelist() describe __MY_AWL Sender has been seen before. priority __MY_AWL -300 meta MY_HAM_SC (( BAYES_00 + __MY_AWL ) > 1) describe MY_HAM_SC Clearly not SPAM. priority MY_HAM_SC -200 tflags MY_HAM_SC nice score MY_HAM_SC -50 shortcircuit MY_HAM_SC on However this does not work as messages which get BAYES_00 and AWL, do not get Short Circuited... I presume that this is because the AWL which normally runs at a priority of 1000 can't be accessed at an earlier stage? I still want the AWL to do its normal job once the other scoring has finished, so don't want to make its priority less than 1000, but was hoping that there was a way to query its information earlier in the SpamAssasssin process..... Any ideas? -- View this message in context: http://www.nabble.com/How-to-query-the-AWL-at-an-earlier-stage-for-Short-Circuit--tf4332696.html#a12339661 Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
