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.
SECURAWALL MAILFLOW
How SecuraWall MailFlow Works
Follow domain ownership verification, MX setup, SMTP destination configuration, message filtering, temporary queuing and delivery retries.
CLOUD-BASED EMAIL SECURITY & CONTINUITY
No appliance. No hardware purchase. Simple guided setup.
SecuraWall runs in the cloud. Keep your current mail server and mailboxes; configure your domain and DNS from the portal. Free Setup Assistance is included in every package.
- 1. ChooseSelect your package and verify domain ownership.
- 2. ConnectFollow the package-specific MX and delivery-target instructions.
- 3. VerifyConfirm delivery, then manage your service online.
SMTP Relay add-on also requires approved SMTP credentials and sender DNS configuration. DNS propagation and your mail-provider settings affect activation time.
How your package works
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
1 · Register and verify
Choose one package for your domain, verify your account email and publish the ownership TXT record. Complete payment and keep the proof record published.
2 · Configure the package receiving route
Backup MX keeps the primary MX records and adds a less-preferred secondary. For Email Protection, publish only gate.securawall.com after saving and verifying a manual real-server destination. Never route delivery back to the gateway.
3 · Queue, protect and deliver
Package 1 queues and forwards without content scanning. Package 2 applies enabled protection and quarantine policies to incoming email routed through the gateway. Destination outages defer delivery; recovery restarts delivery.
4 · Add optional SMTP Relay
An administrator approves sending. Create an enabled SMTP device account and authorize sender domains. Verify SPF before payment, then use the advertised SMTP port and selected TLS mode. DKIM signing is optional and recommended.
Filtering · Email Protection
Spam and malware policies decide whether a message is accepted, rejected or held. Antivirus controls depend on global and domain settings; encrypted contents cannot be inspected.
Temporary queue and retry
Eligible accepted messages wait in the SMTP queue when delivery temporarily fails. Retries follow the configured schedule; permanent rejections and queue expiry have different outcomes.
Follow the result
The portal displays recorded SMTP destination acceptance, current queues and observed protection events. Destination acceptance is not proof of inbox placement or user reading.
Verify your setup before relying on it
Publish the exact TXT ownership token and keep it published. For Backup MX, keep the legitimate primary MX records and add the less-preferred secondary. For Email Protection, publish only gate.securawall.com as your MX record and configure a separate manual delivery target for your actual mail server. Verify that destination before switching DNS.
Plan a controlled outage and recovery test for your own domain. The public diagnostic tools inspect DNS and SMTP observations; they do not send a test email or prove recipient acceptance.
Read the complete setup guide