Tobi via Postfix-users:
> Hi list
>
> we have an issue that we're currently not able to solve because of the
> precedence of postfix maps. From the manpage I get that the order is
>
> For recipient domains in the default domain class: In order of
> decreasing precedence, the delivery transport is taken from 1)
> $transport_maps, 2) $sender_dependent_default_transport_maps or
> $default_transport.
>
> in our transport_map we have a dedicated nexthop config for all our
> customer domains.
>
> Now the problem is that we want to route bounces (especially locally
> generated bounces) to our customer domains via a dedicated bouncer
> system. So my first thought was to create a map for bounces
>
> @ smtp:[our.bouncer.tld]:25
>
> and add it as sender_dependent_default_transport_maps to main.cf
>
> But this does only work if the RCPT domain has no entry in the
> transport_maps as transport_maps has precedence and therefore always
> "wins" if rcpt domain is in there.
>
> Does anyone have a creative idea how to solve that?
>
> Thanks for any input/idea/voodoo-magic ;-)
The 'content_filter' feature and FILTER actions in
access tables or header/body_checks take precedence
over the above.
If the bounces arrive via SMTP, an access map like
<> filter smtp:[our.bouncer.tld]:25
check_policy_service can produce the same result.
Otherwise it may be difficult.
Wietse
_______________________________________________
Postfix-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
