On Mon, Feb 12, 2024 at 09:05:12PM -0600, Jakob Cornell via Postfix-users wrote:
> Can we improve this so it's easier to get this right on the first try
> as a newcomer, and make it more clear what's happening at run time? It
> looks like a code change to skip the logging along with the actual
> table lookups might be in order, and some clarification in the docs.
> I'm happy to create patches for some docs changes at least if that's
> useful. Not sure what the contribution policy of the project is.
That'd be a layer-violation. The logging code lives outside the
individual table drivers and with "_maps" parameters that support
multiple tables, above any individual table lookup. It does not
make a lot of sense to push the logging down into each table.
Some tables support partial keys, other do not, as documented
under in regexp_table(5):
TABLE SEARCH ORDER
Patterns are applied in the order as specified in the table,
until a pattern is found that matches the input string.
Each pattern is applied to the entire input string. Depending on
the application, that string is an entire client hostname, an
entire client IP address, or an entire mail address. Thus, no
parent domain or parent network search is done, and user@domain
mail addresses are not broken up into their user and domain
constituent parts, nor is user+foo broken up into user and foo.
--
Viktor.
_______________________________________________
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
