On Wed, Feb 26, 2014 at 02:59:25PM -0800, Quanah Gibson-Mount wrote:
> Fiddling with how Zimbra sets some variables that get pushed to
> postfix, and trying to determine if transport_maps is order
> dependent.
>
> I.e., are these equivalent:
>
> transport_maps =
> lmdb:/opt/zimbra/conf/postfix/postfix_discard_domains,
> proxy:ldap:/opt/zimbra/conf/ldap-transport.cf
>
> transport_maps =
> proxy:ldap:/opt/zimbra/conf/ldap-transport.cf,
> lmdb:/opt/zimbra/conf/postfix/postfix_discard_domains
For all "mumble_maps" parameters and for any given lookup key, the
tables listed are searched in order, and the first match terminates
the search.
Some lookup features are documented to use partial keys, as for
example with transport lookups, where the first key is the full
address, then the domain alone (the "*" entry is separately looked
up as a default).
With multiple lookup keys each key in turn is looked up in each
table until some table matches at which point the lookup is done.
done := false
for each sub-key until done
for each table until done
if result := lookup(sub-key, table) is not null
done := true
Beware of wildcard tables, listed last, matching the full key (e.g.
regexp for any address) with earlier listed tables listing only
partial keys (e.g. domains).
--
Viktor.
