On 26/07/2014 03:32, Axb wrote:
> On 07/25/2014 07:26 PM, Kevin A. McGrail wrote:
> On 7/24/2014 9:42 PM, Noel Butler wrote: Hi, Is there a way to get the return
> code in the generated reports? eg: uridnssub ALT_URI bl.foo A
> 127.0.0.2-127.0.0.11 body ALT_URI eval:check_uridnsbl('ALT_URI') describe
> ALT_URI URL's domain A record listed in bl.foo ($RETRUN_CODE) score ALT_URI
> 3.0 tflags ALT_URI net a so if the check matched on 127.0.0.6, desc would be
> describe ALT_URI URL's domain A record listed in bl.foo (127.0.0.6) Thanks
> for any pointers Nothing currently in the code Looks like you would have to
> modify URIDNSBL.pm to add that info in the sub got_dnsbl_hit to add to the
> test_log data From looking, $str contains the return data so likely need to
> look through $uris and add $str to this line: $pms->test_log ("URIs: $uris");
> Let us know if it works and perhaps it's worth adding to the codebase.
what's the advantage of such a response method?
The idea of separate return codes is to use different rules/scores and
different rule descriptions which describe the type of listing
As you see, we use .2-.11 for this rule, the RC is only for internal use
here so support can identtify which list, (we have two others that use
singular codes that are rule specific) so are you suggesting that rather
than that one rule, we have ten rules doing exactly the same thing?
That's not very efficient :)
