>Your blacklist is independent of spam filtering, yes? So when a blacklisted >sender submits a message you can reject at rcpt time for the recipients who
>don't want to receive from that sender.
Yes, and even for the case where other addresses are aliases or forward to a user
who has blacklisted the sender, an extra check on the local delivery router is straight
forward enough too. The advantage of the acl is it saves time and processing power for
the simple case.
>What do you do about aliases? If a local alias expands to two recipients with different
>whitelisting options for the sender, how do you handle it? This is the main thing that's
>stopping me taking the final step to full scanning at smtp time.
Yes, I had thought about that and decided, for now, to leave it. But the solution that would
work using my method would be to remove all whitelisting from the acls and to always
accept spam.
Then you have to do all your filtering at routing time, setting up :fail: routers for certain
conditions at the right point in the routing list. It is all _possible_ but seems rather
nasty and tedious to configure. That is why I'm suggesting some kind of built-in
whitelisting feature would be very helpful.
With regard to smtp time scanning, I think that it would still beadvantageous in this case
as it does very simply mean you only scan each message once, even if it has 100
recipients.
