Ronald F. Guilmette:
> P.S. I am agnostic with respect to the level of specificity
> required. For example if I sent something to <myrfriend...@yahoo.com>
> and then that address became whitelisted for _all_ local recipient
> addrsses, I think that would acceptable, even if (as should be
> obvious) it might possibly be better to have that address only
> be _selectively_ whitelisted, i.e. just for <r...@tristatelogic.com>.
>
> Either way, an automated whitelisting thing would be useful...
>
> ... but only if it works with Postfix.
Amavisd has a pen pals feature that should work with smtpd_proxy_filter.
This requires a shared read/write database (MySQL, I believe).
In the case of a Postfix-only solution, whitelist updates could be
generated by mis-using smtp_generic_maps, relocated_maps, etc. (add
an address if it isn't already "known") and they could be queried
with check_sender_access (look up a "known" address).
Before lmdb support was added in Postfix 2.11, there was no good
way to safely share a persistent Postfix database between read-only
processes and read/write processes. So, it should be no surprise
that there at thius time no Postfix features that share a database
between read/write clients (smtp_generic_maps, relocated_maps, etc.)
and read-only clients (check_sender_access).
Wietse
