> Looking in the configuration options, I see:
>
>   whitelist_to [EMAIL PROTECTED]
>
> which says that all the mail to [EMAIL PROTECTED] will be whitelisted
> - no spam
> will be sent (I still don't understand the more_spam_to and all_spam_to
> stuff, but hey).

Actually it doesn't really mean this at all. It means that all messages to
that address get 6 points subtracted from their score, which has the effect
of whitelisting slightly spammy messages. Using more_spam_to subtracts 20,
and all_spam_to subtracts 100.

> There are also "whitelist_from" and "blacklist_from". What I
> would love to
> have is a "blacklist_to", which would turn SA on for the passed
> [EMAIL PROTECTED] In essence:

I would like a blacklist_to also, but I'd prefer that it simply added 6
points to the score (the opposite of whitelist-to). Since whitelisting
doesn't turn SA off, there's no sense in a blacklist turning it on.

> Caveat: How does SA handle execution order? If I:
>
>    whitelist_from [EMAIL PROTECTED]
>    blacklist_from *@disobey.com
>
> Which takes precedence?

Neither, since both are just score modifiers. The effect would be to
subtract 100 from the score for [EMAIL PROTECTED] and add 100 to the score
for all other addresses (effectively cancelling out the whitelist_from but
also marking everything from all other users as spam)

Have you looked at using SQL for your solution? You can have virtual users'
preferences in the database, and have a default setting in local.cf of
"required_hits 200". Then for users who opt in, just add a "required_hits
7.0 (or whatever) to the database for their address.

If you're using vpopmail the new vpopmail stuff should let you do that
without a database.

Otherwise, if there was a blacklist_to that added 100 to a score, you could
use it like you're saying. You'd use all_spam_to to subtract 100 from all
scores for the domain, then blacklist_to to cancel that out for specific
users. I wouldn't use whitelist_to because a score of 6.0 isn't enough to
completely "opt out".

Have you considered that SA in its default configuration is an "opt in"
system anyway? Since it marks messages and doesn't filter them, you could
run it sitewide and let users opt whether to act on SA's headers.

--
michael moncur   mgm at starlingtech.com   http://www.starlingtech.com/
"Research is the process of going up alleys to see if they are blind."
                -- Marston Bates


_______________________________________________________________

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: [EMAIL PROTECTED]
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk

Reply via email to