Exclude a Single User from Sending Outbound through CloudFilter

Description

The CloudFilter outbound relay is designed for human-to-human communication rather than for transactional messages, bulk mail, or mass mailing. Using the relay for transactional or high-volume sending can negatively affect the reputation of shared CloudFilter outbound transport addresses, leading to delivery issues and potential blocklisting. 

Outbound mail that exhibits this behavior, or other unhealthy sending patterns, may be flagged and temporarily held for review by CloudFilter to help protect the deliverability of the shared transport environment. Partners and their customers should use a dedicated email marketing platform for transactional or high-volume email distribution whenever possible. 

If a third-party mailing platform is not an option, selectively routing those users outside of the Mailprotector outbound connector so that mail is sent through Microsoft's outbound relay, or outbound mail route so that mail is sent through Google Workspace's outbound relay, should be considered only as a last-resort alternative. 

CloudFilter is platform-agnostic and works with any email system. If a domain uses an email platform other than Microsoft 365 or Google Workspace, there may not be a way to route around MailProtector's outbound configuration. Feel free to contact MailProtector Support for guidance. However, we may advise you to contact the domain's email platform provider for further assistance.

Applies to: CloudFilter, Microsoft 365 (O365, M365), Google Workspace (G Suite)

Microsoft 365: Exclude a User from the CloudFilter Outbound Connector

The Mailprotector outbound connector must be configured and enabled before following these instructions.

Filtering, logging, SecureStore archiving, and Bracket encryption will not be available for outgoing messages of an address that is routed around the outbound connector.

 

 

Google Workspace: Exclude a User from Mailprotector Outbound Routing

The Mailprotector outbound mail route must be configured before following these instructions.

Filtering, logging, SecureStore archiving, and Bracket encryption will not be available for outgoing messages of an address that is routed around the outbound connector.

 

 

Related to

Updated

Was this article helpful?

0 out of 0 found this helpful