https://issues.apache.org/SpamAssassin/show_bug.cgi?id=4900
--- Comment #14 from John Hardin <[email protected]> 2010-04-15 20:54:11 EDT --- (In reply to comment #13) > As to John's addition in comment 10: > > This could also be reasonable shortcut fodder. If the fixed score has > > been set to (for example) -500, it's unlikely any combination of spam > > rules will push it back above zero. > > No dice. Here's what that does: > > 1 -235.000 > 2 -102.500 > 3 -58.333 > 4 -36.250 > 5 -23.000 > 6 -14.167 > 7 -7.857 > 8 -3.125 > 9 0.556 > 10 3.500 > 11 5.909 That isn't shortcutting (bypassing scan) when the AWL average is very negative/positive, which is what I was suggesting. Shortcutting on AWL totscore is admittedly a more intrusive change than simply tweaking the numbers the AWL data gets set to, but shortcutting would indeed make it a permanent white/blacklist, not just a "white/blacklist for the next month or so". It would also break GTUBE, because a large negative AWL score that shortcut scanning would bypass the GTUBE rule, unless we provide something like a tflag for "this rule can't be bypassed by AWL shortcut" and apply it to GTUBE. It would also break the "averager" part of AWL, absent such a tflag, but use of that flag reduces the permanence of the white/blacklisting. GTUBE also should not count towards AWL score or you'd risk blacklisting someone who sends a GTUBE... Yep, rather intrusive. > How about we set the AWL totscore to -100 and the count to 10 rather > than 1? > > 1 -35.000 > 2 -29.091 > 3 -24.167 > ... > 6 -13.333 > 9 -6.111 > 12 -0.952 > 13 0.455 > 14 1.739 > 15 2.917 > 16 4.000 > 17 5.000 > 18 5.926 > > Not enough in my book. Push the envelope harder. Try setting totscore to -950 (to pass GTUBE) and count to 500 or 1000. -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
