Why are we doing this
I was challenged with finding a solution to split up our incoming mailflow and push it through separate content filters. As we’re trying to split mails within the same domain we were unable to make this decision within a single postfix instance as it would only read a single transport map.
Therefore we’ve chosen to run multiple instances to make decisions based on a 1st and 2nd transport map. The reason we need two transport maps is because besides the content filter split we also use different applications as endpoints for certain mail addresses.
How are we going to do this
…we need to enable postfix multi instance.
We’re calling the second instance postfix-delivery as that’s what the main goal of the instance will be. We keep the initial postfix instance to decide which content filter the mail gets routed to.
####Initiate MultiInstance postmulti -e init ####Create Secondary Instance postfix-delivery postmulti -I postfix-delivery -e create ####Enable Secondary Instance postmulti -i postfix-delivery -e enable
…we need to configure the new instance’s main and master configs.
The main instance will run on port :25 and transports to the filters default ports. The filters will return the mail to the second instance on port :100025. This way we can transport mail based on two transport maps and have granularly control over which mail goes through which filter.
The transport map of the (initial) postfix instance running on port :25 would look like following:
firstname.lastname@example.org smtp:secondaryfilter.domain.com:25 email@example.com smtp:secondaryfilter.domain.com:25 * smtp:primaryfilter.domain.com:10024
This will route the mails to the specified filters whereas our primary filter is a Amavis cluster and the secondary filter a third party solution. As we are “Proof Of Concept”ing this we wanted to have control over the addresses that go through the third party solution. Both filters will return their mail to the second postfix instance listening on port :10025. This instance has the following transport and recipient canonical map:
* smtp:[aspmx.l.google.com] firstname.lastname@example.org smtp:[22.214.171.124]
Recipient canonical map:
email@example.com firstname.lastname@example.org email@example.com firstname.lastname@example.org
2019-09-19 13:19 +0000
6daeb13 @ 2019-09-24