On Fri, Nov 12, 2021 at 09:06:11AM -0500, Wietse Venema wrote:
> Mirko Vogt:
> > transport_maps =
> > pipemap:{proxy:mysql:/etc/postfix/sql/mysql_transport_maps.cf,
> > inline:{FOO=BAR}}
> ...
> > Is postfix complaining about the "proxy:mysql:" transport setting within
> > a pipemap-chain expected behaviour or potentially a bug? If the former,
> > may I ask about the reasoning?
>
> If you look at the default setting for proy_read_maps, then you
> will see that it does not contain
> "proxy:mysql:/etc/postfix/sql/mysql_transport_maps.cf". Instead
> it contains that string inside pipemap{}.
>
> The proxy_read_maps fature uses a generic list matcher that knows
> nothing about Postfix maps, that does not look inside pipemap{}.
> That would require a dedicated matcher.
I have a fix that will be released in Postfix 3.7 soon, and in a few
weeks in Postfix 3.4 .. 3.6.
In the meantime, a possible workaround would be to replace
pipemap:{proxy:mysql:/path/to/file.cf, inline:{FOO=BAR}}
with
proxy:pipemap:{mysql:/path/to/file.cf, inline:{FOO=BAR}}
Wietse
