On 16/01/2026 16:52, Viktor Dukhovni via Postfix-users wrote:
On Fri, Jan 16, 2026 at 10:18:24AM -0500, Wietse Venema via Postfix-users wrote:
Wietse Venema via Postfix-users:
Could you use "postconf -x"?
This feature is available with Postfix 2.10 and later.
And then,
postconf -x proxy_read_maps (as of 20260111, expands 103 parameters)
postconf -x proxy_write_maps (as of 20260111, expands 4 parameters)
give an almost complete view of main.cf settings, while
postxonf -xP '*/*/proxy_read_maps'
postconf -xP '*/*/proxy_write_maps'
do the same for any overrides in master.cf.
But master.cf may also have variour map-valued overrides, for tables
that aren't necessarily proxied. One of my master.cf entries has:
-o { smtpd_client_restrictions = ... }
with what happens to be a simple "inline:{{key = value}}" table, but
it could have other content.
Handling master.cf is tricky, any "-o { foo = bar }" value could be
relevant of "foo" overrides a parameter that may hold table references,
though at least with "psotconf -xP" the values are expanded, and I
expect that expansions take any other overrides in the same master.cf
entry into account. So the complixity is knowing which overrides to
worry about.
Limiting to proxy_read_maps and proxy_write_maps does risk losing some
things that need changing. The script I posted should be able to handle
the case of
-o { smtpd_client_restrictions = ... }
John
_______________________________________________
Postfix-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
