Hi,
Rather, Postfix address rewriting makes multiple queries against
whatever tables are configured, using various fragments of the input
address as documented for virtual(5), aliases(5), canonical(5), etc.
Sorry, I still don't get it :-(
If everything is tried anyway, then what's the reason of having `%s`,
`%u` and `%d` at all?
And can these additional queries be disabled somehow?
You're referring to this part at https://www.postfix.org/virtual.5.html
- right?
Each query pattern is sent to each specified lookup table before trying
the next query pattern, until a match is found.
I think you should repeat this info on
https://www.postfix.org/pgsql_table.5.html too, cause with this being my
setup in `main.cf`:
local_recipient_maps = pgsql:/etc/postfix/pgsql_local_recipient_map.cf
... I didn't look at virtual(5), aliases(5), canonical(5), cause those
didn't seem relevant.
# About postgresql:// connection URI:
You should explain that such URIs are parsed by Postgres (not Postfix) -
cause this is certainly not obvious for everybody. Then add a link to
https://www.postgresql.org/docs/current/libpq-connect.html#LIBPQ-CONNSTRING
(which indeed does explain it nicely), and that's it.
In the example, use a string with as many parts as possible (password,
multiple options, etc.), cause for users it's always easier to delete
stuff than to find out how to append stuff.
# About encoding = LATIN1:
If you shorten this:
Historically, the database client was hard coded to use LATIN1 in an attempt
to disable multibyte character support.
This feature is available in Postfix 3.8 and later.
to:
This feature is available since Postfix 3.8. Before, the database client was
hard coded to use LATIN1.
Then it would be clearer IMO :-)
--
Cheers,
Thomas
_______________________________________________
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
