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 =
pipemap:{proxy:mysql:/etc/postfix/sql/mysql_transport_maps.cf,
inline:{FOO=BAR}}
however postfix complains about it stating
warning: request for unapproved table:
"mysql:/etc/postfix/sql/mysql_transport_maps.cf"
warning: to approve this table for read-only access, list
proxy:mysql:/etc/postfix/sql/mysql_transport_maps.cf in
main.cf:proxy_read_maps
which seems quite odd, given that the "proxy:mysql:" setting works fine
without the pipemap around.
I then tried to add
"proxy:mysql:/etc/postfix/sql/mysql_transport_maps.cf" to
$proxy_read_maps explicitly, when realising, I can't simply add, but
only (re)set variables (please correct me if I'm wrong here).
Trying to get away from copying all the default values for
$proxy_read_maps, I tried
proxy_read_maps = $proxy_read_maps
proxy:mysql:/etc/postfix/sql/mysql_transport_maps.cf
which states
warning: unreasonable macro call nesting: "proxy_read_maps"
fatal: dictionary mail_dict: macro processing error
which I have to say I do not find unreasonable at all :)
Anyway, I now ended up with
proxy_read_maps = [output from `postconf -dfh proxy_read_maps`]
proxy:mysql:/etc/postfix/sql/mysql_transport_maps.cf
which does the job, however feels at least a bit clumsy.
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?
Thanks a lot
mirko
