Greg Sims:
> I placed the following post from Wietse in our main.cf -- let's call
> this "mx_access":
>
> # There is a crude way to automatically group messages by destination
> # MX hosts, but that works only for the special case that all messages
> # have exactly one recipient or all recipients in the same domain.
> #
> # /etc/postfix/main.cf:
> # check_recipient_mx_access pcre:/etc/postfix/mx_access
> #
> # /etc/postfix/mx_access:
> # /\.outlook\.com$/ FILTER outlook:
> # # other patterns...
> #
> # That will send a message to outlook if any MX looks like outlook.
>
> We want to use our Postfix setup for the devotion email (always
> exactly one recipient) AND transactional email which is unpredictable.
> The words "crude" and "special case" are a bit unnerving for the
> transactional email use case. What happens if we use "mx_access" and
> a transaction email arrives with multiple recipients of different
> domains? If I can gain confidence about the side-effects of using
The FILTER action overrides the routing of all recipients of a
message. For example, if one message has outlook and non-outlook
recipients, then all recipients would be sent to outlook.com,
including the non-outlook ones.
Wietse
> "mx_access", I will likely switch from our current "transport_maps"
> approach to "mx_access" for two reasons: truly dynamic as Viktor
> points out and a much simpler/smaller map file.
