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
Backup MX with Google Workspace: Plan Before Adding MX
Evaluate secondary routing, forwarded-mail authentication and receiving policies without assuming universal compatibility.
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.
Separate outage access from queued delivery
Google Workspace already operates a cloud mail service. Backup MX does not provide Gmail mailbox access when users cannot sign in. Decide whether the need is temporary queuing for your own receiving infrastructure or a different continuity requirement before purchasing an additional route.
Preserve legitimate MX records
Keep the published records required by your Workspace setup. Do not copy another company’s targets or replace working primary MX with a backup gateway. One SecuraWall domain plan can evaluate several eligible primary targets; domain and destination checks remain necessary.
Receiving gateway settings need review
Google documents inbound gateway configuration using public gateway addresses and source-IP handling for authentication. The Workspace administrator must evaluate these settings for the real message path. Do not enable an inbound restriction that blocks legitimate direct mail while retaining direct primary MX, and do not bypass filtering globally to force acceptance.
Collect delivery evidence
Use a mailbox you control and a uniquely identified test message. Inspect the backup queue outcome and the receiving service’s mail logs and authentication results. Distinguish a temporary 4xx delay from a permanent 5xx rejection. A remote SMTP acceptance still does not promise inbox placement.
Tested configuration, not a provider logo
This guide does not assert a tested integration for your organization. Confirm the topology and policies with the Workspace administrator, perform a controlled test and document rollback before relying on secondary delivery. The free DNS tool is an observation aid, not a Gmail delivery test.
References and service conditions
Related guides
Backup MX, SPF, DKIM and DMARC
Why forwarded email can fail authentication, how sender rewriting helps and where its limits remain.
Read guide →Backup MX with Multiple Primary Mail Servers
Plan secondary routing for several legitimate primary destinations without loops or extra domain subscriptions.
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 →