[Maia-users] default protection settings confilct with settings.php behavior

[Robert LeBlanc]

Russ Ringer wrote:

> Commenting this out in both files allows this behavior which I think
> is very useful. I don't understand the reasoning behind preventing
> this functionality. 

Mainly it's designed as a safeguard to prevent you from setting
thresholds and destinies that are incompatible with one another.  Once
you decide on a destiny (quarantine, discard, label) for spam, the
thresholds that make sense for that destiny become limited.

What you (and other more advanced users) really want is a system that
lets you map a different destiny to different score ranges, rather than
just performing one action on anything that's considered "spam".  Rest
assured that this is already in the works.  The upcoming reworking of
the threshold/destiny system will offer a lot more flexibility in that
regard, including score ranges for "high-probability spam",
"low-probability spam", "high-probability non-spam" and "low-probability
non-spam", and configurable destinies for each.

-- 
Robert LeBlanc <rjl at renaissoft.com>
Renaissoft, Inc.
Maia Mailguard <http://www.maiamailguard.com/>

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: OpenPGP digital signature
Url : http://www.renaissoft.com/pipermail/maia-users/attachments/20060921/7916501d/attachment.bin