On 7/3/2015 9:56 AM, John Gateley wrote: > Hi, > > I've found several websites for configuring backup MX servers > that recommend setting the transport_maps for the primary domains. > This seems wrong to me: the DNS MX record already has this info. > Is there another reason to set the transport_maps for the backup > config? > > Thanks > > John > > http://www.linuxmail.info/postfix-backup-mx/ > http://www.linuxpcfix.com/how-to-set-up-a-postfix-mailserver-as-a-backup-mx-mail-exchanger/ > > http://www.linuxlasse.net/linux/howtos/Postfix_as_backup_MX > http://www.akadia.com/services/postfix_mx_backup.html >
(I didn't read the links) You might use a transport map if you want to control where mail from the backup to the primary goes, such as sending to an alternate IP, or maybe just want to avoid a DNS lookup. But if you're sending to the same IP as published in DNS, no real reason to use a transport entry. Note secondary MX servers are no longer considered a benefit. They are spam magnets, they must have their own list of valid recipients, and are generally more trouble than they are worth. The one exception for this if if you happen to be located somewhere off the grid where network or power outages are frequent, and likely to last more a couple days. Even then, you're better off renting a gateway server in a data center and configuring it with a long queue lifetime. -- Noel Jones
