Place the gateway deliberately in the mail path
Fortra Secure Email Gateway is the current mail-gateway offering associated with Clearswift. It is relevant where the organisation needs a defined inspection and policy point in message flow. Selection must account for inbound and outbound routes, hosting arrangements and the legitimate content that must pass through the gateway.
Inventory mail platforms, relays and external sending dependencies. Identify required handling for messages, attachments and sensitive information, while distinguishing optional capabilities from the base configuration. A gateway is not merely a mailbox setting: changes to routing, certificates and resilience can affect the availability of business communication.
Commission message handling as well as inspection
Confirm the supported deployment and current product specification. Define the response when a component or external dependency is unavailable, along with the rollback method. The installation scope should identify who owns DNS, mail connectors, certificates and the surrounding network configuration.
Pilot representative attachments, application notifications and approved policy test cases. Verify the selected reject, hold, release or other supported actions, including the handling of uncertain or encrypted content. Review false positives with business owners rather than silently widening exceptions. Handover needs the mail-flow diagram, policy set, release process, administrative access and operating instructions. If MMC is expected to maintain the gateway or review incidents, specify that scope separately from equipment or software supply.
Evidence to request for this scope
- Obtain a deployment diagram and current gateway options for the intended mail platform.
- Test legitimate attachments, outbound policy and authorised release or restoration.
- Demonstrate agreed routing failure behaviour and the controlled rollback procedure.