https://issues.apache.org/SpamAssassin/show_bug.cgi?id=4900
Greg Troxel <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #9 from Greg Troxel <[email protected]> 2010-04-14 08:29:06 EDT --- I have wanted different behavior in AWL as well. I think the basic issue is that in addition to AWL, which I think works well for what it is, that there should be database entries that can assign a score bias to some addresses, and to have those not get adjusted. These entries should perhaps be independent of AWL. So I'd be able to do spamassassin --assign-score [email protected] -5 and then there'd be a db entry matching that sender that would add -5 points. One could use -100 or +100. (But, with forgeable senders, -5 feels right to me to rescue legit mails that look spammy but not give a total pass.) To implement this the AWL db could store the score in the scorefield and -1 in the count field, and then AWL would ignore the entry. But, AWL and persistent scores probably should both operate. -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
