https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6890
Bug ID: 6890
Summary: Allow 'override threshold score' in spamc
Product: Spamassassin
Version: SVN Trunk (Latest Devel Version)
Hardware: All
OS: All
Status: NEW
Severity: minor
Priority: P2
Component: spamc/spamd
Assignee: [email protected]
Reporter: [email protected]
Classification: Unclassified
Created attachment 5130
--> https://issues.apache.org/SpamAssassin/attachment.cgi?id=5130&action=edit
Proposed patch 1
I attach a proposed patch to this bug, for the spamc client which I have tested
- it seems to be working well. It's based off the latest SVN I got from:
http://svn.apache.org/repos/asf/spamassassin/trunk
It adds the option -T to allow the spam threshold value to be overridden, which
changes when spamc will return 0/1 to indicate spam, but does *not* change any
of SpamAssassin's message rewriting.
The reason I think this change is a good idea is that I (and perhaps others)
find myself wanting to be able to define a "grey area" of e-mails, where they
are rewritten as spam but not completely discarded. This can be done by
setting the threshold override higher than the normal SpamAssassin threshold.
For example, if you want the grey area to be between 3.0 and 8.0, you'd set the
normal SpamAssassin threshold to 3.0, then call spamc with the threshold
override of 8.0. Scores under 3.0 would be OK; spamc returns 0 and the message
is not rewritten. Scores between 3.0 and 8.0 would be "grey area" - spamc
still returns 0 (so a shell script will not discard it), but the message *is*
rewritten. It will be delivered to the user's mailbox as a rewritten message.
Remaining scores would cause the message to be rewritten *and* spamc would
return 1, allowing a shell script to discard it.
--
You are receiving this mail because:
You are the assignee for the bug.
