SecuraWall MailFlow Frequently Asked Questions

Your mailboxes remain on your existing server. Backup MX adds a secondary MX. Email Protection uses SecuraWall as the only published MX and a separately configured manual delivery target.

No. Delivered messages leave the queue. This service provides temporary storage and delivery during outages.

Create your account, verify your email and domain ownership, then complete 3D Secure credit card payment on this site; your bank may open a verification screen. Renew manually each calendar month; no automatic charge. Daily reminders begin three days before expiry. If unpaid, acceptance and queued delivery pause 24 hours after expiry.

Temporary queuing of eligible incoming SMTP messages and delivery attempts to your existing destination. It does not include hosted mailboxes, webmail, outbound access or a recoverable mailbox archive.

Backup MX: USD 15.00 per domain per calendar month, taxes included in the displayed service price. Renewals are manual. Checkout shows the payable amount and currency; receiving and payment-provider restrictions may apply.

The current published plan allows up to 14 days in the delivery queue. Check the settings applied to your domain. Queue age continues while delivery is paused; expired messages are not an archive.

No. The published retry interval is approximately 3 minutes. Receiving rate limits, temporary errors, DNS problems and service checks can delay delivery. A retry interval is not a delivery SLA.

The current published limit is 50 MiB for the complete encoded message (52,428,800 bytes). Attachment encoding and headers count toward it. Your domain may have a lower limit.

No. There is no per-message billing charge or advertised count cap, but storage is finite and shared. There is no reserved per-domain capacity. Acceptance remains subject to available resources, active service and security policies.

No. The plan is per domain, not per MX hostname. Keep legitimate primary MX records and review the eligible destinations. Equal MX preferences or multiple hostnames do not prove independent infrastructure.

Backup MX provides queuing and delivery only. Email Protection includes Backup MX plus AntiSpam, Antivirus and quarantine. SMTP Relay is an optional paid add-on to either base package on the same domain. Select it during new-domain checkout or add it later. It does not include incoming protection.

No. Rewriting helps the SMTP envelope forwarding path, but does not guarantee DMARC alignment, receiver acceptance or inbox placement. Receiving connectors or policies may need administrator review and controlled testing.

A missing or changed ownership TXT can pause new mail acceptance and queued delivery. Keep the current proof published. Queue age continues during pauses; consult the authenticated domain security view for the current state.

Confirmed deletion permanently purges queued and held messages. If one queued message has recipients in multiple domains, purging it also removes it for every other pending recipient. Read the confirmation before deleting.

No. Supported file contents are analyzed statically for actual VBA and suspicious macro heuristics. Macro presence, suspicious heuristics and incomplete analysis have separate actions. A filename extension alone does not confirm that a file contains a macro. Office analysis is static; it does not execute files in a sandbox or reconstruct their contents.

For eligible protected incoming mail, domain actions are managed in Domains / Settings / Advanced Threat Signatures. The domain can inherit server defaults or use an override. The administrator scanner must be ready and AntiSpam enabled. These actions exclude Backup MX and authenticated outgoing SMTP.

An authorized personal user can request IT review of an eligible held message. IT sees pending requests and can receive configured email notifications. A request does not release the message. Elevated-risk holds require IT review and fresh release checks; a local SMTP submission is not proof of inbox delivery.

When explicitly enabled for a protected domain, supported body links open a SecuraWall check screen. Current registration, package, configured blocked domains and public DNS addresses are checked again before Continue. Administrator-managed blocklists apply. When enabled, static inspection checks supported pages and redirect destinations, and Google Web Risk Lookup adds URL reputation checks. Checks run at click time and again on Continue. If enabled inspection is incomplete or the Google check fails or reaches its local quota, Continue is unavailable. URLs sent to Google include their paths and query parameters. A URL that is not listed may still be unsafe. JavaScript is not executed. Rewriting changes message bodies and can invalidate original DKIM/ARC signatures downstream. Test receiving-server compatibility before broad activation. Unsupported messages follow the saved wrapping failure policy.

For eligible protected incoming mail, IT administrators configure protected names and approved sender addresses per domain. A different Reply-To alone does not block mail. Local static checks combine bank-change and pressure language with identity or reply-address signals. Explicit saved policies select Accept, Quarantine or Reject; false positives are possible. Approved addresses do not bypass authentication or other checks. BEC-policy holds require IT review.

The Logs page separates email traffic from account activity. Eligible recorded changes show named old and new values without password values. Customers see their own account scope; older history can contain less detail.

Public MX preferences, TXT, SPF text, NS, SOA, address and IP reverse-DNS observations. The DNS lookup sends no email. You can optionally test an MX target on the same page to observe SMTP connection, greeting and TLS results without submitting a message. These observations do not validate recipients, the current account ownership token, message authentication, service activation or final delivery.