A secure email gateway (SEG), also called a secure mail gateway, sits in the email delivery path and applies security policies before messages reach the receiving mail system. For a business that already has Microsoft 365, Google Workspace or its own mail server, a cloud gateway can add an incoming inspection layer while the existing platform continues to host mailboxes.
The buying decision starts with a simple distinction: email security controls what is accepted; email continuity manages what happens when a destination is unavailable. A product may combine both, but the two functions should be checked separately.
Where a cloud secure email gateway fits
In a typical gateway deployment, the public MX records direct incoming mail to the gateway. The gateway inspects a message and follows the configured decision: accept it for delivery, hold it in quarantine or reject it. Accepted mail is forwarded to a configured receiving destination.
The destination must remain a real receiving route, rather than a hostname that sends mail back to the gateway. Receiving-side controls may also be needed to prevent senders from bypassing the inspection path. Moving MX records without planning the destination can create a delivery loop or leave an unintended direct route.
What to compare beyond the feature name
A useful evaluation asks what each check actually does, when it runs and what users can do afterward. “Phishing protection” is too broad to answer those questions on its own.
- Incoming checks: Which spam, antivirus, link, attachment and impersonation checks are enabled and supported?
- Quarantine: Who can review held mail, request release and approve delivery?
- User management: Can the organization maintain quarantine users manually, import a CSV or use a supported connector?
- Continuity: What happens to accepted mail if the destination stops responding?
- Operational visibility: Can administrators trace a message’s queue and delivery outcome?
Gateway filtering, mailbox hosting and outbound relay
These are different services. A gateway routes and inspects incoming SMTP traffic. A mailbox platform stores users’ mail and provides their email interface. An outbound SMTP relay provides a sending route for authorized systems. Buying one does not automatically supply the others.
For example, a company keeping its existing mailboxes might need incoming protection first and an optional outgoing route for devices later. Separating those requirements makes pricing and setup responsibilities easier to assess.
How SecuraWall Email Security is scoped
SecuraWall Email Security is a Cloud Secure Email Gateway with supported incoming checks, personal quarantine and Backup MX continuity included. Quarantine users can be managed through manual setup, CSV import or supported connectors: Google Workspace, Active Directory, LDAP, OpenLDAP, Zimbra API and Carbonio API.
Checks depend on enabled policies, supported content and inspection limits. A gateway cannot promise that every threat will be detected. Unsupported or encrypted content can limit inspection, and service scope should not be confused with a sandbox or a complete mailbox archive.
A practical selection checklist
Write down the current mailbox provider, the receiving destination, who will administer quarantine and how outage handling should work. Then compare those needs against the actual service scope and current limits. A controlled rollout should verify normal delivery, quarantine behavior and recovery from a receiving-server outage before the configuration is considered complete.
Start with the Email Security service, compare it with standalone Backup MX, or use the product comparison table to separate incoming protection, continuity and outbound relay.