About MX-Based clusters

To use an MX-based cluster to inspect your outbound mail, you can define an equivalent MX preference for each
Network Prevent for Email
Server in the cluster. If load balancing is required, each record should have the same priority value and point to the fully-qualified domain name (FQDN) of one of the
Network Prevent for Email
Servers. Any MTA that sends a message to the
Network Prevent for Email
Servers goes to one of the servers in the cluster.
If the
Network Prevent for Email
Servers operate in reflecting mode, they reflect messages back to the IP address of the MTA from which the messages arrived. If the
Network Prevent for Email
Servers operate in forwarding mode, they forward messages to the host or IP addresses that you configure. MX record lookups can also be performed for valid DNS names configured in the next-hop MTA list.