On Fri, Jan 16, 2026 at 12:37:43PM -0500, Wietse Venema via Postfix-users wrote:
> As of Jan 11, there are about 107 parameters that may allow /file/name
> or table:type (attached as text). Based on that demographic, working
> from a list with "examine these parameters" may be more concise
> than working from a list with "ignore these parameters" (depending
> on configuration that list could be 10x longer).
Additional missing parameters are listed in "smtpd_restriction_classes",
my configuration has an access check that uses indexed tables in one of
the restricion classes.
> local_recipient_maps mydestination virtual_alias_maps ...
Another complication are the "domain = " parameters in PgSQL, LDAP and
MySQL tables, these are string matchlists, an in principle could
reference external files tables. As, e.g., noted in ldap_table(5):
domain (default: no domain list)
This is a list of domain names, paths to files, or "type:table"
databases. When specified, only fully qualified search keys with
a *non-empty* localpart and a matching domain are eligible for
lookup: 'user' lookups, bare domain lookups and "@domain"
lookups are not performed. This can significantly reduce the
query load on the LDAP server.
domain = postfix.org, hash:/etc/postfix/searchdomains
It is best not to use LDAP to store the domains eligible for
LDAP lookups.
NOTE: DO NOT define this parameter for local(8) aliases.
This feature is available in Postfix 1.0 and later.
I don't expect that many users do much except list literal domain names
there, but perhaps a few adventurous souls decices to take advantage of
the additional indirection (hopefully not by consulting yet another
LDAP table...).
--
Viktor. 🇺🇦 Слава Україні!
_______________________________________________
Postfix-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
