https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6890
Karsten Bräckelmann <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|blocker |enhancement --- Comment #7 from Karsten Bräckelmann <[email protected]> --- Frankly, I don't like the idea of adding such decision / override option to spamc. First of all, spamc is meant to be a light-weight client, merely feeding messages to the daemon, and dealing with the result in an absolute minimal way. spamc deliberately does not decide about the score, nor rewrite the message or even add headers. That is entirely left to spamd. Thus, if a feature like this would be implemented, I am strongly in favor of dealing with it in spamd. Moreover, this basically duplicates existing functionality, and introduces the notion of "discard" -- something SA does not do. SA scores, but it does not deliver, nor discard. The environment described in comment 0 is almost identical to adding the X-Spam-Level header, which is not by coincidence meant to easily allow for this shades of gray differentiation. The only difference between this existing behavior and the request is, what the spamc calling tool acts upon -- the $is_spam return value, instead of grepping for a single line. Changing, overriding the decision (exitcode) whether a message is deemed spam or not in this way seems pretty confusing, too. A message's score exceeding the required_score threshold is classified spam. The return value of spamc should not claim anything else. Setting Severity back to enhancement, as Jez, the reporter, even set it himself. I don't see how this would be a blocker. -- You are receiving this mail because: You are the assignee for the bug.
