Jan Johansson:
> Let's say that for various reasons a system ends up having two
> identical entries in transport maps.
By definition you can't have that in a hashed file, *SQL database,
or LDAP. Other Postfix lookup tables such as regexp or pcre will
return the first match, as documented.
Wietse
> Is there a fixed logic as to which takes precedence?
>
> As an example (I entered my own address instead of the address in question):
> j...@mupp.net smtp:mail.kontinuitet.com
> j...@mupp.net smtp:haven.skyddsrummet.net
>
> Right now it _appears_ as the second choice is the one used, is that
> something that can be taken for granted? I have gotten the impression that
> transports are evaluated until the first match?
>
> Naturally the correct solution is to stop the backend system from having
> duplicated data, and that will be the case eventually. But for the moment
> that is just how things are.
