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 exp
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 r
Hello,
I'm having a working virtual user/mailbox setup, where I use mysql as
database backend and query it via "[..]_maps = proxy:mysql:[..]"-settings.
I now played around with the lookup table type "pipemap", wrapping the
previous setting(s) within a pipemap chain, e.g.
transport_maps =
