SecuraWall MailFlowEmail Security & ContinuityCloud Email Security, Backup MX and optional SMTP Relay.
SecuraWall menu

EMAIL SECURITY · PACKAGE 2

Email quarantine management for users and IT

Quarantine keeps a held message separate from normal delivery while authorized people review it. SecuraWall provides distinct IT and personal mailbox views, with access restricted to the current customer, domain and recipient scope.

An everyday example

A user finds a held invoice in personal quarantine and asks IT to review it. IT can inspect the recorded decision and available message preview. Elevated-risk holds require IT review and fresh checks before an authorized release.

Illustrative scenario; this is not a live message or a detection-rate claim.

How it works

  1. Hold by policyA configured security rule selects quarantine. The held state is separate from a delivery retry caused by the receiving server being unavailable.
  2. Review the right messagesIT manages authorized domain messages. A mailbox user sees eligible held mail for the primary address and authorized linked aliases.
  3. Release or removeAuthorized release submits the message for delivery after required checks. It does not prove acceptance by the destination or placement in the inbox.

What your IT team can control

Manual and CSV provisioning

IT can create local users manually or validate a CSV preview before import. Existing users or aliases from any source cannot be replaced by CSV; missing CSV rows do not delete accounts.

Personal credentials

The system generates local passwords and queues a personal access email to the registered user, with no IT copy. First sign-in requires a password change. Local users can request a reset without IT choosing or seeing the password.

Aliases, quotas and package access

Aliases share primary credentials and quota. Personal quota overflow remains held for IT review. After a downgrade to Backup MX, retained users cannot access quarantine; the retained-user IT view is read-only.

Coverage and responsibilities
  • Only held mail within current account, domain-registration and recipient authorization is visible. A display name or MIME To header does not grant access.
  • Content retention remains subject to the configured quarantine lifetime and storage limits. A hold or release does not restart the original message age.
  • Directory synchronization and Google corporate sign-in are not currently provided. Local access accounts do not create mailboxes on your receiving mail server.

Choose the incoming security gateway

Email Security requires SecuraWall as the only published MX and a separate real receiving destination. Your mailboxes remain with your provider. Backup MX does not include these inspection or personal quarantine controls; the SMTP Relay add-on does not enable incoming protection.

Explore Email Security Compare pricing

Related setup and protection

Chat on WhatsApp