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 distinction? It doesn't state
which table types are indexed, and in the database readme only a few types are
called out as indexed. (My testing indicates the 'inline' type is indexed, but
I can't find mention of this in the documentation.)
While the documentation for 'check_recipient_access' in postconf(5) links to
access(5), it doesn't mention the indexed table type distinction, implying the
lookup sequence for indexed files is used regardless of the table type:
check_recipient_access type:table
Search the specified access(5) database for the resolved RCPT TO address,
domain, parent domains, or localpart@, and execute the corresponding action.
And then there's the confusing logs from my original email which appear to show
the full lookup sequence being done on a regexp table. My assumption is that
the full lookup sequence is actually being processed, but individual lookups
beyond the first one are being skipped without skipping the corresponding
logging code.
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.
Jakob
_______________________________________________
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
