> That's close to what I use. However, MX entries alone aren't the > solution. You also have to configure the mail servers to forward the > mail on to the final destination once it comes back online. I'm not sure > how to do that myself, and don't really have to time to put much effort > into it since my mail server is only for small scale personal use. I > just use dyndns.org's "Backup MX" service: > http://www.dyndns.com/services/mailhop/backupmx.html. Even if that isn't > a solution for you, it's at least a place to start looking. >
Patrick is correct here, if you can, use a third-party service. They will always (sometimes?) have higher maintenance standards than stuff that you do. However, this is _very_ simple with postfix. MX for mydomain.com mydomain.com mail is handled by 10 server1.mydomain.com. mydomain.com mail is handled by 20 server2.mydomain.com. mail server 1: Accepts mail for mydomain.com mail server 2: Postfix, with relay_domains = mydomain.com mydestination = server2.mydomain.com maximal_queue_lifetime = 30d bounce_queue_lifetime = 1d - Maximal queue lifetime affects how long it reties delivery. - Bounce queue lifetime will help alleviate problems with spammers overflowing the bounce queue. -- gentoo-user@gentoo.org mailing list
