[pfx] Re: Per recipient sender access via an access policy delegation server

On 12/05/2026 21:52, Wietse Venema via Postfix-users wrote:
> John Fawcett via Postfix-users:
>> Hi
>>
>> I'm posting this message in case anyone would find it useful to have an
>> access policy delegation server that implements per recipient sender access.
>>
>> I have been using check_sender_access as a deny list for senders that I
>> want to block from sending me email, usually emails that started off as
>> legitimate but after unsubscribing still keep coming. The issue is that
>> when I block a sender, I do so for any recipients that use the server,
>> not just me. While in practice that hasn't caused many issues, it always
>> worries me that I might block email other users want to receive.
> Would a postfwd policy ruleset handle that?
>
> Unlike access maps that give an answer based on a single property,
> policy lookups support multi-criteria decisions by design.
Yes, I think you're right that existing policy delegation servers can 
also handle this. Nevertheless I tried a different design with a single 
process managing multiple connections via python selectors which use 
various underlying methods such as epoll on Linux rather than a forking 
or preforking model. Not sure how that will compare for performance or 
reliability or whether I will even notice the difference on my low volumes.
>> [snip]
John
_______________________________________________
Postfix-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]