SA Bugzilla – Bug 6530
Evaluate Tiopan DNSBL
Last modified: 2012-08-13 08:05:04 UTC
http://www.tiopan.com/blacklist.php The owner of the Tiopan DNSBL has requested that we test his blacklist in our weekly masscheck. http://www.sdsc.edu/~jeff/spam/cbc.html This weekly comparison of blacklists indicates that it has decent performance. header RCVD_IN_TIOPAN_BL eval:check_rbl('tiopan-lastexternal', 'bl.tiopan.com') describe RCVD_IN_TIOPAN_BL Received from an IP listed in Tiopan Blacklist tflags RCVD_IN_TIOPAN_BL net nopublish score RCVD_IN_TIOPAN_BL 0.01 As agreed last year, I am proposing this here for public comment before adding more DNSBL's for masscheck comparison. Unless I hear any objections or "please wait", I'd like to commit this to the sandbox before this Saturday's masscheck.
Warren, As best I can tell this was committed. Is it running afoul of bug 6527 for testing? Any feedback on the rules? Regards, KAM
Tiopan's safety is atrociously bad so it will likely never be suitable for Spamassassin. But it often gives unique results that are nothing like other DNSBL's so it is interesting to keep in the weekly masscheck.
(In reply to comment #2) > Tiopan's safety is atrociously bad so it will likely never be suitable for > Spamassassin. But it often gives unique results that are nothing like other > DNSBL's so it is interesting to keep in the weekly masscheck. Roger that. Then closing this ticket as won't fix since it won't be released.
I'd like to propose removal/disabling of these test from sandboxes ( /trunk/rulesrc/sandbox/wtogami/20_bug_6530_tiopan.cf) They're set to nopublish (since 2010) and while it's nice to test new BLs, it puts an unnecessaary load on weekly masschecks to keep them there for such a long time. comments, votes please!
+1 Any BLs that are active in sandbox with no one actively reviewing the results should and really must be disabled. Net masschecks are taking too long on the weekend!
FTR: Rules commented out on Aug 12 2012