On Wed, 18 Mar 2026 08:29:40 -0400 (EDT) Wietse Venema via Postfix-users <[email protected]> wrote:
> Sad Clouds via Postfix-users: > > I looked at: > > https://www.postfix.org/POSTSCREEN_README.html#temp_allow_sharing > > > > However it does not seem to fit in with my use case. Specifically, I > > would prefer each server to have its own allowlist and regularly > > replicate recent changes across. The Postfix memcache does not seem to > > support this. > > Memcached (the back-end) does not support replication. And indeed, > Postfix generally does not implement database replication (the only > Postfix database replication is the built-in backup support from > memcache to another database). > > Unlike mailboxes (or mail queues) the loss of a postscreen_cache > does not result in the loss of mail. There is no need to obsess > about replicating postscreen_cache updates, especially when > the number of MX hosts is small, like 2. > > Wietse > _______________________________________________ > Postfix-users mailing list -- [email protected] > To unsubscribe send an email to [email protected] OK thanks for the info. I'm trying to avoid a scenario with greylisting and DNS load balancing, where SMTP client is temporary rejected on mail1.example.com, then rejected again on mail2.example.com, etc., since the SMTP servers are not aware of each other's postscreen allow lists. I may just completely avoid deep protocol tests with postscreen. They may result in long mail delivery delays when load balancing across multiple servers. _______________________________________________ Postfix-users mailing list -- [email protected] To unsubscribe send an email to [email protected]
