Viktor Dukhovni via Postfix-users:
> 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.
Restriction classes are already scanned in Postfix 3.12 proxymap
(and soon in 3.11), but it still misses:
- parsing xxx_table configuration files (/file/name and type:table
in domain parameter, backup database name in memcache_table)
- parsing master.cf (evaluating -o overrides in the right context)
These will not be in Postfix 3.11.
The complexity is in part due to the current Postfix configuration
model where each feature decides for itself how to interpret
unstructured text. Postfix was implemented before libxml (expat)
existed, and years before YAML and JSON.
> 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...).
All configuration will be replaced with a Generative AI plugin...
Wietse
_______________________________________________
Postfix-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
