https://issues.apache.org/SpamAssassin/show_bug.cgi?id=4900
--- Comment #15 from Adam Katz <[email protected]> 2010-04-16 11:03:26 EDT --- (In reply to comment #14) > 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". Oh, you're talking about an actually persistent setting. Sounds like dangerous waters. I'd rather that stay in the config file as whitelist_from et al. > 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. > > GTUBE also should not count towards AWL score or you'd risk blacklisting > someone who sends a GTUBE... Good point. The GTUBE rule already has tflags userconf and noautolearn. There is no tflag to bypass AWL, but if we move its priority so that it fires after AWL, that would do the trick, no? > > How about we set the AWL totscore to -100 and the count to 10 rather > > than 1? > > Push the envelope harder. Try setting totscore to -950 (to pass GTUBE) and > count to 500 or 1000. Maybe you missed the bottom of my last comment? I tested count=100 for a 30-point ham. After 100 subsequent emails, it still scored only -2.663. I didn't report it, but a trial run of count=100 against a 10-point ham took 1001 runs to hit 5 points. I think count=100 and totscore=-100 is fine (or perhaps even too strong); we don't want to go overboard, otherwise there's no difference between AWL and actual white/black lists. We also don't want to be ruled by corner-cases like a 30-point ham. Also noted at the bottom of my last comment, my take on GTUBE's intent is that it is scored 1000 specifically to override all negatives, especially including something like AWL whose data isn't locatable via grep. As long as we immunize AWL from it, I think it's irrelevant. GTUBE was designed to test spam flagging, not how to save a 1000-point ham. -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
