I'm no Postfix guru but I'm using this on the backup mx. Suppose your domain
is example.com.
/etc/postfix/main.cf:
transport_maps = hash:/etc/postfix/my.tables/transport
/etc/postfix/my.tables/transport:
example.comsmtp:[primary.example.com]:12345
.example.comsmtp:[prima
In message
Paul Goyette writes:
> While researching to see if I could find a way to fix my other issue
> (how my primary-MX server can differentiate between messages originating
> on my backup-MX server and those that are simply relayed from elsewhere)
> I thought maybe I could configure the bac
Well, I think I spoke too soon.
I do have the dual-transport mechanism set up. But I still have a
"classification" problem!
On the backup-MX machine, I would like to have the equivalent of
if (message_origin == local) then
relay via transport1
else
OK, I got this working! (Persistence pays off...)
On the backup MX, I made sure that $mydestination was correctly set, and
then set $local_transport to "smtp:nexthop:port"
On the primary server, I created a new smtpd transport (listener)
[:::::x]: inet n - n -
On Sat, 16 Jan 2016, Viktor Dukhovni wrote:
On Sat, Jan 16, 2016 at 04:00:48PM +0800, Paul Goyette wrote:
my_smtp:12345 inet n - n - - smtpd
But it's not clear to me if this syntax will define a new listener (in
which case this would belong on my primary-MX machine) or if this
On Sat, Jan 16, 2016 at 04:00:48PM +0800, Paul Goyette wrote:
> my_smtp:12345 inet n - n - - smtpd
>
> But it's not clear to me if this syntax will define a new listener (in
> which case this would belong on my primary-MX machine) or if this would
> enable an _outgoing_ connection to
While researching to see if I could find a way to fix my other issue
(how my primary-MX server can differentiate between messages originating
on my backup-MX server and those that are simply relayed from elsewhere)
I thought maybe I could configure the backup-MX to use two different
smtp transport
