Thomas Landauer via Postfix-users:
> Hi,
>
> yeah, I think the docs about the connection are clearer now :-)
>
> However, the "three queries behavior" is still undocumented IMO. I did
The three queries are documented in the virtual(5) text.
Postfix has a layered architecture for table lookups.
- Table-driven mechanisms such as SMTP server access maps, local
recipient maps, canonical_maps, virtual_alias_maps, transport_maps.
These can generate multiple requests for table lookup mechanisms.
- Table lookup mechanisms such as hash, btree, pgsql and a ton of
other ones. These know nothing about acces tables, local recipients
and so on.
> But my point is: If somebody is configuring the database lookup at
> `local_recipient_maps`, they will not read those docs about virtual
If the local_recipient_maps description is incomplete then that can
be fixed, just like the pgsql_table(5) text.
> 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.
Configure Postfix to query both databases, and give each Postfix
pgsql file its unique "domain = whatever" setting. The queries will
then hit only the relevant database, and they will never see
those fragment queries for @domain and for the address localpart.
Wietse
_______________________________________________
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
