> The solution: Change the way it reports on the subject line, and let it > all through.
That's how I handle most of my stuff... > In PerMsgStatus.pm (which is where the subject line is changed) I am > adding two additional variables: _SPLV_ and _SPLG_. > Spamlevel = hits/threshold (so hits of 15 with threshold of 10 = 1.5, > hits of 15 with threshold of 5 = 3, hits of 4, threshold of 5 = 0.8). > I then have a table (Using an if statement): > 1.2 <= Possible > 1.7 <= Likely > 1.7 > Definitely. So this is essentially creating additions to the current "score" variable, right? How hard would it be to get spamassassin to handle deletions, etc according to either score or spamlevel? Anyway, I personally think that at least the ranking (possible/likely/etc) is an awesome idea. Especially if those thresholds could be manually modified/renamed/added by each user in their personal prefs. My only concern would be that with higher score thresholds, a direct ratio probably wouldn't be the best way of handling things. A logarithmic scale of some sort would probably paint a more accurate picture, since it's much more likely that a spam would score 10 out of 5 than 50 out of 25, etc. -Chris ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Gadgets, caffeine, t-shirts, fun stuff. http://thinkgeek.com/sf _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
