Cloud Backup MX: Choosing a Secondary Mail Exchanger

What Cloud Backup MX means

Cloud Backup MX is a secondary mail exchanger hosted separately from your receiving mail server. It can accept eligible incoming SMTP messages and hold them temporarily while delivery to your configured destination is unavailable. Cloud describes where the gateway operates; it does not mean cloud mailboxes, an email archive or a second copy of every message. Messages delivered directly to your primary MX never enter the backup queue.

Start with the failure you need to cover

An on-premises receiving server may become unreachable during a connectivity problem, power interruption or planned maintenance. An independent secondary route can be useful for those situations. A mailbox login problem or an outbound sending failure needs a different solution. Check whether your primary provider already has resilient receiving infrastructure, and decide which remaining failure warrants an additional route. Different hostnames alone do not establish independent infrastructure.

Plan DNS and the real destination

Keep legitimate primary MX records and add the backup target with a higher preference number than all intended primaries. Lower numbers are preferred. Publish the current ownership TXT token and keep it after activation. SecuraWall automatic delivery discovers eligible primary MX targets and excludes its own gateway; manual delivery selects a configured public destination. Neither mode should resolve back to the backup gateway. Multiple primary targets use one domain plan rather than one subscription for every MX hostname.

Compare limits rather than unlimited slogans

Review the current price, complete encoded message-size limit, queue lifetime and retry interval on the pricing page. Storage is finite and shared, with no reserved per-domain allocation. A missing ownership proof or service suspension can pause processing while queue age continues. Retried delivery is not an exact schedule or a guaranteed deadline. Delivered, expired or deleted messages are not a recoverable mailbox backup; confirmed deletion also purges affected shared queued messages for other pending recipients.

Validate forwarding before relying on it

Your receiving system must accept legitimate forwarded mail from the gateway. Sender rewriting can help forwarding SPF checks for the SMTP envelope but does not guarantee DMARC alignment or inbox placement. Cloud-provider connectors and gateway policies need administrator review. A TCP connection and SMTP greeting establish reachability, not acceptance of a real recipient. Use a controlled message to a mailbox you own, compare receiving logs and test recovery during an authorized maintenance window.

Choose and operate with evidence

Use an independent account email so that notifications do not depend on the protected mail server. Document original DNS, receiving policy, service dates and rollback. Check the oldest queued message during an outage and restore the actual destination before expiry. The Domain Check tool helps inspect public routing records and optional SMTP/TLS observations; it cannot prove delivery or validate your current ownership token. Select Backup MX for temporary SMTP queuing, and evaluate a separate continuity product if users need outage mailbox access.

References and service conditions

• SMTP: RFC 5321
• Null MX: RFC 7505
• Current plan limits
• Security responsibilities