http://issues.apache.org/SpamAssassin/show_bug.cgi?id=3109
------- Additional Comments From [EMAIL PROTECTED] 2006-04-13 14:46 ------- (In reply to comment #48) > how's about getting rid of "shortcircuit ham"/"shortcircuit spam", and just > have either "shortcircuit default" (renamed to "shortcircuit on") or > "shortcircuit off" behaviour as the available options? Then the score alone > is used to determine whether a rule shortcircuits as ham or as spam -- negative > means ham, 0 or positive spam. > if brevity of the configuration is the aim, we can still support "shortcircuit > ham" / "shortcircuit spam", but just implement them in the config-reading > subroutine as translating to "shortcircuit on / score -100" or "shortcircuit > on / score 100". > What do you think? sounds reasonable to me. on/off is simple, and still gives you the flexibility to control the final score. also it would probably be best to set noautolearn tflag by default, and force someone to tflag learn a s/c rule. if you have on|off|ham|spam, the ham and spam s/c classification could score - 100/+100 and force autolearning. but i guess that puts us right back where we started at ham|spam|default|off really... just changing "default" to "on", and making sure "on" has noautolearn tied to it. i'd rather not have to define a rule with 6 lines of config if we can set some sane defaults. body RULE /text/ describe RULE blah score RULE x.x shortcircuit RULE on tflags RULE noautolearn priority RULE -100 i would suggest shortcircuit "on" set noautolearn tflag and -100 priority by default.... and if you want to adjust the priority higher from there, you have to specify it, and if you want to autolearn on that rule, you either have to specify the learn tflag, or you have to s/c ham|spam. i guess if you s/c as ham|spam, the noautolearn tflag would have to be removed from the rules config. d ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
