Having 12x that text in the postconf masnpage would not help.
Certainly not, but I think there's a good middle ground. A more practical
change would just make brief reference to the distinction. For example:
check_recipient_access type:table
Search the specified access(5) database for
Hi Wietse,
I can add a debug log that a specific table is skipped for a specific name.
Ah yes, that's a better fix. That would take care of my confusion with the
logging.
Do you have any thoughts on postconf(5) describing partial key lookups in the
descriptions for check_*_access without
The logging code lives outside the individual table drivers and with "_maps"
parameters that support multiple tables, above any individual table lookup.
Oh I see. Well without rearchitecting the logging it seems this could be made
more intuitive for the case where all of the maps in a
Thanks Viktor. I found what I believe you're referencing in the access(5) man
page:
With lookups from indexed files such as DB or DBM, or from networked
tables such as NIS, LDAP or SQL, patterns are tried in the order as
listed below:
Is this the only documentation explaining this
Hi folks,
I'm updating the configuration of my mail server and having problems with a
regexp table. This is the relevant configuration in main.cf:
smtpd_recipient_restrictions =
check_sender_access regexp:/etc/postfix/db/sender_access_table
...
And
