Are you using redundant mail server(s) in form of an mx fallback server to collect all incoming mails if the ordinary mailserver happens to be offline?
Currently I only have one mailserver (SmarterMail v5.5) with external backup which makes it possible to restore it pretty fast on new physical server, if needed. However, in the meantime as well as if I have to restart that server, no mail is received at all - just bounced back to the sender.
Therefore I'd like to install a mx fallback server, which I've understood I can use the free version of smartermail to be. Then all incoming mail will be stored at that server instead and will try to send this mail queue to the frontend server after a period of time, and when that ordinary mailserver is back online again no mail will be lost at all for any customer.
The big question here is: How should I configure the DNS server for this - how do YOU have it configured? This also affects DNP since I'd like to set the proper DNS configuration when a new domain is added in the control panel, configured in the smartermail settings in server setup in DNP.
My frontend mailserver is using IP *.132 and in DNP server settings I currently add these dns settings for smartermail (ip address partly replaced with # signs):
mail A ###.###.###.132
MX 10, mail.[DOMAIN_NAME]
TXT v=spf1 a mx -all
This way every user gets an mail.customersdomainname.tld to be used both as POP server configuration in mail clients as well as for webmail.
Now - according to SmarterMail instructions I've understood it as I'm supposed to add another MX record here with higher priority. The question is how this should look like - any experiences from this? My MX fallback will be located at ip ###.###.###.131
I'm guessing it could be something like this for another DNS post to add - however I'm not very good at DNS configuration, I have to admit:
MX 21, mailbackup.myhostingdomain.tld
Should there be any A record as well, or (if I'm right in my guess above) will all mail adressed to a mail account at mail.customersdomainname.tld automatically be forwarded to the new dns post's adress mailbackup.myhostingdomain.tld automatically, if the .132 server is offline? If so - besides this, I only have to configure the DNS server with the A record (and MX as well) for mailbackup.myhostingdomain.tld to point at the .131 server, right?
Alternatively:
Maybe I should use a dns post as follows instead:
MX 21, mailbackup.[DOMAIN_NAME]
mailbackup A ###.###.###.131
But this maybe messes up the free version of Smartermail at the mx fallback server (.131) if host headers follows as well (!?) containing more than one single domain name (mailbackup.myhostingdomain.tld) since it would mean every customer's every domain name would follow, preceeded by the mailbackup prefix of course. I don't think this alternative is the proper way to go, but I'd like to hear what you other guys say and how you've configured your system.