Package 1 · Backup MX
Secondary MX, temporary queuing during destination outages and automatic delivery on recovery. No mailbox pre-check, AntiSpam, Antivirus, content inspection or quarantine.
TECHNICAL GUIDES
Queue Incoming Email During Mail Server Maintenance
Prepare a controlled maintenance window, verify backup routing and observe recovery without promising uninterrupted mailbox access.
Package 2 · Email Protection
Primary MX gateway with configurable AntiSpam, Antivirus, sender-domain checks and quarantine. Publish only gate.securawall.com and configure a separate manual receiving target. Queuing and recovery remain included.
Optional SMTP Relay add-on
Add authorized outbound delivery to either Package 1 or 2 for the same domain. Separate add-on pricing, approval, server credentials, quotas, TLS and verified SPF apply. Customer-domain DKIM signing is optional and recommended. Incoming protection remains determined by the base package.
Explore packages and add-ons
By the SecuraWall team · Updated · Operational guidance, not a delivery guarantee.
Decide what maintenance affects
Describe whether the work interrupts your receiving SMTP server, network, mailbox access or outbound sending. Backup MX addresses temporary incoming delivery to an unavailable destination; it does not keep staff signed in or provide an outage webmail client. Select a window and a rollback owner.
Verify the route before the window
Keep legitimate primary MX records, verify the ownership TXT and review the saved delivery targets and active service period. Use a recipient you own to test the backup route before depending on it. Record the original DNS and receiving configuration outside the protected domain.
Budget queue time and capacity
Compare the planned outage with the lifetime and message-size limit actually applied to your domain. Existing messages may already be old. Shared storage is finite, and receipt is subject to service and security conditions. A maintenance plan needs room for both the outage and any recovery delay.
Observe accepted messages
During the controlled window, follow queue count, oldest age, destination error and system notices. Do not interpret every new queue item as a service failure. Do not repeatedly flush the entire queue or create replacement messages to force a receiving server past a temporary rate limit.
Restore and verify the destination
After the work, restore the authorized destination and inspect retry results. Confirm real mailbox arrival with receiving-side logs and the controlled test message. A remote SMTP acceptance is useful evidence, but not a universal inbox placement guarantee. Keep your rollback available until validation is complete.
Close the window with evidence
Record what was changed, which test succeeded, the messages still queued and any permanent rejection that needs recipient or policy correction. Check ownership and service dates again. Use an independent contact address for alerts rather than depending on the mail server under maintenance.
References and service conditions
Related guides
How to Test Backup MX Safely
Validate your own domain, queue behavior and recovery without treating an open port as successful delivery.
Read guide →Backup MX Queue Retention and Deletion
Understand message age, expiry, paused delivery and permanent queue removal.
Read guide →Backup MX Delivery Troubleshooting Checklist
Identify whether a delay comes from service state, DNS, routing, SMTP rejection or final mailbox handling.
Read guide →