http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5187





------- Additional Comments From [EMAIL PROTECTED]  2006-11-27 06:52 -------
Here are the current results.

0.00000  37.2752   0.0123   1.000    0.99    0.00  RCVD_IN_XBL   
0.00000  21.3403   0.0144   0.999    0.96    0.01  T_E_RCVD_IN_XBL   
0.00000  21.3403   0.0144   0.999    0.96    0.01  T_RCVD_IN_XBL   
0.00000   2.4869   0.0041   0.998    0.88    0.00  RCVD_IN_SBL   
0.00000   1.8986   0.0082   0.996    0.85    0.00  T_RCVD_IN_ZENXBL   
0.00000   1.4006   0.0041   0.997    0.85    0.00  T_RCVD_IN_ZENSBL   
0.00000  27.0548   0.2362   0.991    0.77   (n/a)  __RCVD_IN_ZEN   
0.00000  27.0416   0.2382   0.991    0.77   (n/a)  __RCVD_IN_SBL_XBL   

This is odd.  T_RCVD_IN_ZENXBL and T_RCVD_IN_ZENSBL are coming out
quite badly here.

The code looks like it should only result in *more* hits for ZENXBL:

header T_RCVD_IN_ZENXBL       eval:check_rbl('zen-notfirsthop',
'zen.spamhaus.org.', '127.0.0.[45678]')

header RCVD_IN_XBL            eval:check_rbl('sblxbl-notfirsthop',
'sbl-xbl.spamhaus.org.', '127.0.0.[456]')

I have a theory: I think the drop-off is because RCVD_IN_XBL and RCVD_IN_SBL
are using #reused results, whereas T_RCVD_IN_ZEN[SX]BL do not. If you look at
the "by contributor" data, this looks likely; compare the net-bb-* results,
which don't use #reuse, to some of the others:
http://ruleqa.spamassassin.org/20061125-r479108-n/%2FRCVD_IN_(ZEN%7CSBL%7CXBL)/detail#all

0.00000   6.5471   0.1378   0.979    0.86    0.00  RCVD_IN_SBL net-bb-fredt
0.00000   6.5338   0.1378   0.979    0.86    0.00  T_RCVD_IN_ZENSBL net-bb-fredt

0.00000   1.6660   0.0000   1.000    0.81    0.00  RCVD_IN_SBL net-theo  
0.00000   0.0005   0.0000   1.000    0.41    0.00  T_RCVD_IN_ZENSBL net-theo

in other words, I need to do a standalone mass-check with --reuse
turned *off* to get a useful comparison of this data.

also: Theo -- looks like you need to look at the resolver on that
machine ;)

finally: no sign of the PBL. odd.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Reply via email to