Configure DNS MX records so that the IMSVA Cloud-Prefilter can intercept mails for scanning.
To configure the DNS MX records for Cloud Pre-filter:
Assume that the following is the current DNS MX record of your-domain.com:
- Retrieve the Cloud Pre-Filter inbound server address from the Domain tab for a policy.
- Click Cloud Pre-Filter. The Cloud Pre-Filter Policy List screen appears.
- Click the name of an existing policy in the Policy List. The Edit Policy screen appears with the Domain tab displaying.
The addresses display in the Inbound Server Addresses area of the Domain tab.
- Modify the MX records as follows:
your-domain.com MX preference = 10, mail exchanger = your-domain.com.eXXXX.gXXXX.ngXXXX.im.emailsecurity.trendmicro.com
your-domain.com MX preference = 10, mail exchanger = your-domain.com.eXXXX.gXXXX.pgXXXX.im.emailsecurity.trendmicro.com
your-domain.com MX preference = 30, mail exchanger = mail01.your-domain.com
your-domain.com MX preference = 30, mail exchanger = mail02.your-domain.com
mail01.your-domain.com internet address = 184.108.40.206
mail02.you-domain.com internet address = 220.127.116.11
After making the modifications to the MX records, Cloud Pre-Filter is the major point of entry for your domain. After the DNS record changes take effect (up to 72 hours), all inbound email message traffic is routed to Cloud Pre-Filter. Your original DNS record information is stored in Cloud Pre-Filter as a backup.
- Modify your DNS MX records to include your own MX as lower priority. This will allow your existing MX records to act as a backup to Cloud Pre-filter
- Ensure you have the same policies enforced on your on-premise IMSVA as the ones in Cloud Pre-filter. The benefit of this duplicate policy is to maintain protection for your business during a rare occurrence of Cloud Pre-filter service being unavailable.
- As our sizing guide recommends, please ensure you have enough onsite capacity to process the full email load for a short time if the Pre-filter is not available.