Email continuity guide

What is Backup MX, and when do you need it?

Backup MX is a secondary mail server that accepts inbound email when your primary mail server is unavailable, holds the messages safely, and retries delivery after your main server comes back online.

Primary MX Your normal mail server, where inbound email should arrive first.
Backup MX A lower-priority mail server that receives mail only when the primary server cannot.
Mail queue The temporary holding area where messages wait until delivery can succeed.

How Backup MX works

  1. 1. Normal delivery Senders try your primary MX first while your mail server is online.
  2. 2. Failover during outage If the primary server is unreachable, mail is sent to the backup MX instead.
  3. 3. Delivery resumes The backup MX keeps retrying and forwards queued messages once the main server returns.

Why businesses use Backup MX

  • Prevent missed inbound email during server outages or maintenance windows.
  • Keep a self-hosted or on-premises mail server without making it a single point of failure.
  • Give staff a way to access mail during downtime when rescue mailbox features are available.
  • Add resilience without moving every mailbox to a completely different email platform.

Backup MX vs ordinary email hosting

Backup MX does not replace your primary mail server. It supports it. Your users still receive normal mail through the main system when it is healthy, while the backup server steps in only during delivery trouble or outages.

What makes a Backup MX service more useful?

Basic Backup MX only queues mail. More capable services can also offer monitoring mode, spam filtering, queue visibility, and rescue mailbox access so users can read and reply while the main mail server is offline.

Protect inbound mail during outages

DNSExit Backup MX queues inbound email when your mail server is down, retries delivery, and can provide rescue mailbox access during outages.

See Backup MX Service Read Backup MX FAQ
Explore by goal

Keep moving with the guide that matches the problem.

Keep remote access working Start with Dynamic DNS when your public IP changes. Fix email delivery Separate outbound sending issues from inbound mail problems. Automate DNS and SSL Use API-driven DNS updates and validation workflows. Compare service options Choose the right email setup before you commit.
;