You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by bu...@bugzilla.spamassassin.org on 2006/11/03 18:45:07 UTC

[Bug 5164] New: Adopt Bob's score-estimation algorithm for sa-update rules

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

           Summary: Adopt Bob's score-estimation algorithm for sa-update
                    rules
           Product: Spamassassin
           Version: SVN Trunk (Latest Devel Version)
          Platform: Other
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P5
         Component: sa-update
        AssignedTo: dev@spamassassin.apache.org
        ReportedBy: jm@jmason.org


 



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

[Bug 5164] Adopt Bob's score-estimation algorithm for sa-update rules

Posted by bu...@bugzilla.spamassassin.org.
http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5164


felicity@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|3.2.0                       |Future




------- Additional Comments From felicity@apache.org  2006-12-05 08:08 -------
sa-update is outside the scope of a release, so just move to future. :)



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

[Bug 5164] Adopt Bob's score-estimation algorithm for sa-update rules

Posted by bu...@bugzilla.spamassassin.org.
http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5164


jm@jmason.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|Undefined                   |3.2.0




------- Additional Comments From jm@jmason.org  2006-11-03 09:47 -------
right now, picking scores for sa-update rules is a bit of a "finger in the air"
thing -- not good.

We could use the perceptron, but I'm hesitant to do that every day or two.  in
particularly, I can see rules fluctuating back and forth due to chaotic effects;
those aren't a big problem once every N months, but every day -- not so good.
also I don't think it's yet possible to run it safely unattended.

Bob Menschel uses (I think) a freqs-based algorithm for SARE rules -- we should
adopt that (or something similar), I think.



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