is per user whitelist/blacklist config and a default whitelist/blacklist possible?

[Ken Anderson]

I've tested the per user configs (see previous message below) and it
seems to work okay. If anyone has any thoughts on this, I'd appreciate it.

Next question: Is it possible to have a combination of per user AND a
default system wide config for blacklist/whitelist rules, so that
user at domain can whitelist and blacklist individual addresses or domains,
but a default ruleset containing common whitelisted addresses is
maintained for the server to allow standard stuff to come through
untouched unless the use specifically blacklists it.
Thanks,

Ken A.


>
> From CustomConfig.pm:
>
> # To enable these functions ....
> #   Is Definitely Not Spam = &ByDomainSpamWhitelist
> #   Is Definitely Spam     = &ByDomainSpamBlacklist
>
> This gives you simple white blacklist functions for TO: *@somedomain.com

> Is there any reason why it wouldn't be a good idea to extend this idea
> to something like this:
>
> Is Definitely Not Spam = &ByEMailAddressSpamWhitelist
>
> That way, you would have full whitelist/blacklist capability on all
> incoming email addresses, since each file would hold the list for a
> single TO: address.
> Thoughts?
>
> Thanks,
>
> Ken A.