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
What Is Backup MX?
How a secondary MX queues incoming mail, where it helps and what it cannot replace.
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.
A queue behind your existing mail system
Backup MX is an additional SMTP receiving route published in DNS. When a sender contacts that route, eligible incoming messages can be accepted into a temporary delivery queue. Your existing mail service still owns the mailboxes and decides whether the recipient exists during delivery. Backup MX does not check whether a mailbox exists before accepting a message. Email Protection may perform a limited incoming SMTP recipient check. SMTP Relay is an outbound add-on and does not add this incoming check to Backup MX. The backup service later attempts delivery to the configured destination. It is not a copy of every mailbox.
When it can help
Backup MX may be useful when an on-premises mail server is unreachable, connectivity is interrupted or maintenance is planned. Configure and test the secondary route before the outage. Simply buying a service after mail has already bounced does not recover those messages.
What a sender decides
A published secondary MX is not a switch controlled by your dashboard. Senders follow their own delivery logic and retry schedules. They may contact secondary servers directly. A permanent recipient or policy rejection is not a promise that another MX will rescue the message.
What to check before purchasing
Confirm that the destination accepts legitimate forwarded messages from the gateway. Read the queue lifetime, complete-message limit and storage conditions. Use an independent contact email, preserve your original DNS settings and test with a recipient you own. Review the paid service period in the portal.
Questions that need separate products
Reading and replying during an outage requires continuity mailboxes or webmail. Restoring previously delivered messages requires a mailbox backup or archive. Authenticated outbound SMTP requires the optional relay add-on, sending approval and credential setup. Packages 1 and 2 require the separately purchased SMTP Relay add-on for relay; hosted mailboxes and archive recovery are not included in any package.
References and service conditions
Related guides
Backup MX vs Email Continuity
Choose temporary incoming-mail queuing or a broader outage workspace based on your real requirements.
Read guide →MX Priorities and Multiple Mail Servers
Understand preference numbers, equal-priority records and secondary MX placement.
Read guide →How to Test Backup MX Safely
Validate your own domain, queue behavior and recovery without treating an open port as successful delivery.
Read guide →Cloud Backup MX: Choosing a Secondary Mail Exchanger
Evaluate a cloud-hosted backup mail exchanger for SMTP outages, maintenance and temporary queuing without replacing your mailboxes.
Read guide →