How to Test Backup MX Safely

Prepare a controlled test

Use a domain and mailbox you own. Record the current primary MX entries and select a maintenance window. Confirm ownership TXT, secondary MX, active service dates and the discovered or manually configured destination in your portal. Do not send probes to unrelated recipients.

Test a real recipient

Send a uniquely identified message through the intended backup route using your authorized test setup. Track its queue ID and inspect the destination mailbox and receiving logs. An SMTP banner or accepted RCPT alone does not demonstrate successful message delivery.

Exercise a temporary outage

In a planned window, temporarily make your own destination unavailable in a reversible way. Send one controlled message and confirm that it remains queued with the expected error. Avoid changing unrelated global firewall or mail policies. Keep a recovery path available.

Restore and observe

Restore the destination, then follow the same message through retry and remote acceptance. Check the real mailbox. Record elapsed time, queue expiry and whether any duplicate messages were received. Retry timing is approximate and receiving-server limits may add delay.

Test policy failure separately

A nonexistent recipient or permanent policy rejection is a different case from an outage. Understand how the destination and backup report that result. If needed, use an authorized test recipient with a deliberately controlled policy rather than generating unwanted delivery failure messages.

Know what remains untested

This exercise does not certify disaster recovery of the gateway, every sender’s MX behavior or inbox placement for all mail. Repeat after material DNS or receiving-system changes. Keep test evidence and support details outside the protected domain.

References and service conditions

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