Viktor Dukhovni via Postfix-users:
> On Mon, Jan 05, 2026 at 12:28:04AM +0100, John Fawcett via Postfix-users
> wrote:
>
> > I am assuming that it is possible to identify all files needing
> > conversion by reading the existing configuration.
>
> Unfortunately, that's not (presently) the case. Many of the affected
> files will be tables used via "check_..._access" in one of the various
> "smtpd_..._restrictions", and these are not inluded in the default values
> $proxy_read_maps or $proxy_write_maps.
There can also be map references in mydestination and other matchlist
like features, plus /file/name entries in matchlists that can contain
more table references.
None of those are currently allowlisted for proxymap which I was
using as a source of truth. Allowlisting those would require an new
match_list helper function to flatten a matchlist.
> Perhaps Wietse will find some way to include the various access-related
> tables and also deal with pipemap: and unionmap: indirection.
Proxymap does already recurse into nested tables such as pipemap
or unionmap, peeks inside "{ maptype:mapname option... }", and it
allowlists tables in smtpd_mumble_restrictions.
But it looks like proxy_*_maps do not allowlist maps in restriction
classes.
Wietse
_______________________________________________
Postfix-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
