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
Set Up SMTP Relay
Configure approved device credentials and sender authentication.
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.
Approve and authorize
Keep Package 1 or 2 active for the same domain, purchase the SMTP Relay add-on, obtain sending approval and create an enabled SMTP device account. Each sender domain must belong to the account and have eligible SMTP Relay rights.
Connect your sending application
Use gate.securawall.com and the configured device username/password. Port 587 supports STARTTLS; port 465 uses implicit TLS. Encryption is mandatory. Plaintext authentication is unavailable on managed submission listeners.
Publish sender DNS records
Add the sending IP to the existing SPF record without creating a second SPF record. If you choose optional customer DKIM signing, publish its exact selector TXT and activate only after verification. Preserve existing provider selectors and DMARC policies.
Verify delivery
Send to a mailbox you control and check SPF, DKIM and DMARC results at the recipient. A local 250 queue response is submission acceptance; remote SMTP acceptance and inbox placement are separate outcomes.