Using the parameter "sender_dependent_default_transport_maps" leads to the same result as using the paramter "sender_dependent_relayhost_maps". I think this is the case cause the recipient domain is also part of the internal domains. Therefore the relay entry defined in the "transport_maps" is taking precedence over "sender_dependent_default_transport_maps" and/or " sender_dependent_relayhost_maps". I need a hint how to overrule the entry definded in the "transport_maps" table for one specific sender.
2015-01-12 18:35 GMT+01:00 Wietse Venema <[email protected]>: > Sebastian Fehrenbacher: > > sender_dependent_relayhost_maps work great when the rcpt to addresses > > domain is not part of the relay_domains. However when both domains - mail > > from and rcpt to - are part of the relay_domains the parameter > > sender_dependent_relayhost_maps is not taking effect. In this case the > > relayhost parameter is used. How can I accomplish sender based routing if > > the sender and the recipient domain of a mail is part of the > relay_domains? > > As documented, the precedence order is: > > sender_dependent_relayhost_maps (default: empty) > > This information is overruled with relay_transport, > sender_dependent_default_transport_maps, default_transport and > with the trans-port(5) table. > > Short answer: maybe sender_dependent_default_transport_maps will > do the job. It has higer precedence than relay_transport. > > [email protected] smtp:example.net > > Long answer: the precedence should be user-controlled. > > Wietse >
