Hi,
yeah, I think the docs about the connection are clearer now :-)
However, the "three queries behavior" is still undocumented IMO. I did
read https://www.postfix.org/virtual.5.html and it is nicely explained
there.
But my point is: If somebody is configuring the database lookup at
`local_recipient_maps`, they will not read those docs about virtual
tables! Why should they?
So I think this should be explained at other places too.
For my own setup, I have just one question:
I have two domains at `mydestination`, and I want a separate database
lookup for each, then pipe the mail to a separate external command.
The transport part works so nicely:
transport_maps = inline:{ foo.com=foo_handler, bar.com=bar_handler }
But for the recipients, I can't see a way of mapping the 2 domains to 2
lookup tables. So my current "workaround" looks something like this:
local_recipient_maps = pgsql:foo.cf pgsql:bar.cf
And then (since both queries will be run) in the SQL do something like:
query = SELECT id FROM table WHERE 'foo.com' = '%d' AND local_part = '%u'
... in order to prevent searching for foo.com's local_part in bar.com's
table.
This will certainly work, but I'm wondering if there's a more
straightforward way than the `'foo.com' = '%d'` hack.
Thanks!!
--
Cheers,
Thomas
_______________________________________________
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
