Wietse Venema:
> > I'm thinking of adding multi-table lookup (similar to canonical_maps,
> > transport_maps, and other _maps features that can search more than
> > one table. Then one could say:
> >
> > check_mumble_access maps:{inline:{key=value, ...}, static:{reject text...}}
> >
> > Being able to search multiple maps can be useful as a general feature.
Based on the analysis in my previous response I have implemented
check_mumble_access {type1:name1, ..., typeN:nameN}
The difference with the syntax in my first reply is that there is
no "maps:" before the "{".
The queries are now implemented with the same code that is already
used for all Postfix features whose name ends in _maps. This
eliminates a problem in the earlier design involving queries for
substrings of a domain name, of an email address, or of a network
address.
If you feel adventurous you can try this patch for Postfix 3.0 and
later. It passes regression tests, but has not been used in real life.
ftp://ftp.porcupine.org/mirrors/postfix-release/experimental/feature-patches/20150725-multi-access-maps.gz
ftp://ftp.porcupine.org/mirrors/postfix-release/experimental/feature-patches/20150725-multi-access-maps.gz.asc
ftp://ftp.porcupine.org/mirrors/postfix-release/experimental/feature-patches/20150725-multi-access-maps.gz.sig
Wietse
