Trellix DLP Network Prevent – SaaS works with a Mail Transfer Agent (MTA) server to protect email traffic.
An MTA server must meet these requirements to integrate with Trellix DLP Network Prevent – SaaS.
The MTA must send all or a portion of email traffic to Trellix DLP Network Prevent – SaaS. Example: In some environments, it might be preferable for Trellix DLP Network Prevent – SaaS to process only mail going to or from public sites, such as Gmail, rather than processing every email sent and received on the network.
The MTA must be able to inspect email headers so that it can distinguish emails arriving from Trellix DLP Network Prevent – SaaS and act on the header strings that Trellix DLP Network Prevent – SaaS adds to the email messages. If certain actions are not supported on the MTA server, do not configure rules on Trellix DLP Network Prevent – SaaS to use these actions.
Your MTA must ensure that email messages received from Trellix DLP Network Prevent – SaaS are routed to the intended destination, and not back to Trellix DLP Network Prevent – SaaS. Example: Routing might be defined using a port number or source IP address, or by checking if X-RCIS-Action headers are present.