> On Sep 29, 2017, at 2:23 PM, Paulo Fraser <[email protected]> wrote:
>
> We send email on behalf of customers as part of our product and run outbound
> only mail servers for this. Thus we send out mail with many different sender
> addresses. Some customers have asked us to relay their mail through their
> servers, which we are happy to do. sender_dependent_relayhost_maps works
> great for this. However, we also have some custom transport_maps in place
> for some recipient domains (e.g. gmail.com) where we do some throttling. The
> problem is that transport maps overrides any sender_dependent_relayhost_maps
> as is documented. Is there any way around this? Can I have rules to relay
> emails to a different server based on sender address as the first priority
> and then for anything that doesn’t match those rules, then apply other rules
> such as transport maps that are recipient based?
Only if you replace sender_dependent_transport_maps with FILTER access(5) rules.
--
Viktor.
