http://bugzilla.spamassassin.org/show_bug.cgi?id=3495

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|blocker                     |major
   Target Milestone|3.1.0                       |3.0.0



------- Additional Comments From [EMAIL PROTECTED]  2004-06-15 13:22 -------
Good news: we have temporary scores for the 3.0 pre-release.

Bad news (?): they are pretty darn high for this rule.

score DNS_FROM_RFC_WHOIS_B 0 1.753 0 2.239

Gauging by my corpus, there do seem to be some TLDs that have problems with
this rule.

I'm going to mark this as a major 3.0.0 issue and I propose removing the rule
as soon as possible.  Removing it is trivial, so I'm not going to post a patch,
just give me a vote.  ;-)

Why just this rule so far?  If I take the network rules and multiply the ham
hit rate by the score, this is the worst rule by a very large factor.

4.53058 DNS_FROM_RFC_WHOIS_B
1.27105 SPF_SOFTFAIL
1.09526 PYZOR_CHECK
1.0047 URIBL_WS_SURBL
0.79205 DNS_FROM_AHBL_RHSBL
0.663026 RCVD_IN_NJABL_DUL
0.579456 URIBL_SBL
0.455742 DNS_FROM_RFC_POST
0.381216 RCVD_IN_RFC_IPWHOIS
0.362691 DNS_FROM_RFC_DSN




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

Reply via email to