https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6525

--- Comment #28 from Warren Togami <[email protected]> 2010-12-29 21:22:44 UTC 
---
> I agree that its has low hit rate, BUT its still valuable for the reasons
> previously mentioned which is why it should stay and you should put creative
> energy in something innovative & worthwile.

Please don't take this personally, but I find your tone to be hurtful.  I am
indeed putting energy into various other "worthwhile" approaches to help
improve spamassassin in different ways.

* Building a better spam trap with 100+ abandoned domain names spread across
multiple servers.  Those feeds are going to different DNSBL's for reputation
data.
* Our masscheck participation seems to be at an all-time low.  Recruiting a
team of nightly masscheck participants who will also help train and recruit
others.  Improving the documentation to make it a far less confusing process.
* Bug #6530: Evaluating Tiopan DNSBL
* Bug #6529: Evaluate Nix Spam DNSBL
* Subject: Floating Scores for Local-Only Rules? trying to find a good use for
Adam Katz' rules.  Comments needed.
* Bug #6527: mkrules erroneously omits nopublish rules from masscheck when
wrapped in ifplugin
* Soon: Analysis: Is deep parsing really a good thing?  (Spamcop mainly.)
* Soon: Discussion about the rule update policies and procedures.  It seems I
am not the only one confused about the current status.

This does not change my opinion that NJABL and rfc-ignorant.org are not
worthwhile for us to keep.  This new question about deep parsing vs.
lastexternal should be investigated.  It is not trivial to test this because
our data on deep parsing is based on --reuse, so I need to test lastexternal
separately with data going forward.

> Where do we draw the line of acceptability?
> It is already 1% weak.  Would 0.5% or 0% be obviously bad enough to warrant
> removal?
> What does this say about the level of acceptability of adding new DNSBL's?

Meanwhile, I would really appreciate opinions on this question from committers.

-- 
Configure bugmail: 
https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

Reply via email to