Configuring DNS MX Records Parent topic

After configuring Cloud Pre-Filter settings and verifying that email traffic is delivered from Cloud Pre-Filter to IMSVA, add the Cloud Pre-Filter "Inbound Server Address" to the MX records for your DNS server. The Cloud Pre-Filter host displays under the Inbound Server Address section of the Domain tab. This is the final step before using Cloud Pre-Filter to scan your email traffic.
WARNING
WARNING
You MUST configure your mail delivery (MX) records to route your email traffic through Cloud Pre-Filter. If this step is not completed, your messages will be delivered to your local servers, and not to Cloud Pre-Filter for scanning.
Tip
Tip
Trend Micro recommends configuring the MX records for Cloud Pre-Filter with a higher priority (specify a lower number) than your existing MX records. Your existing MX records then act as a backup to Cloud Pre-Filter.

Inbound Server Address Parent topic

Cloud Pre-Filter uses the Inbound Server Address to direct email traffic to your IMSVA or your network.
Add the Cloud Pre-Filter "Inbound Server Addresses" to the MX records on your DNS server, not from the IMSVA management console.
To support high availability, load balancing and flexibility for Cloud Pre-Filter, Trend Micro provides Inbound Server Addresses for each domain. Inbound Server Addressprovides an explanation of where you should direct the Inbound Server Addresses for your domains.

Inbound Server Address Example Parent topic

Assume that your domain is example.com. The Inbound Server Address for your domain could be as follows:
example.com.eXXXX.gXXXX.ngXXXX.im.emailsecurity.trendmicro.com
example.com.eXXXX.gXXXX.pgXXXX.im.emailsecurity.trendmicro.com
example.com.eXXXX.gXXXX.sgXXXX.im.emailsecurity.trendmicro.com
Where XXXX is "0001" to "9999".

Inbound Server Address

Address Contains
Points to...
pgXXXX
The address points to your Primary Site.
sgXXXX
The address points to your Secondary Site.
ngXXXX
The address points to your Shared Sites.

Configuring MX Records Example Parent topic

The following process is provided as an example for you to follow when adding the Cloud Pre-Filter "Inbound Server Addresses" to your DNS server’s MX records.
Example Assumptions:
Assume the following is the current DNS MX record for example.com:
example.com MX preference = 10, mail exchanger = mail01.example.com
example.com MX preference = 10, mail exchanger = mail02.example.com
mail01.example.com internet address = 1.1.1.1
mail02.example.com internet address = 1.1.1.2

Procedure

  1. Retrieve the Cloud Pre-Filter "Inbound Server Addresses" from the Domain tab for a policy.
    1. Click Cloud Pre-Filter.
      The Cloud Pre-Filter Policy List screen appears.
      Note
      Note
      Domains that have not had their MX records to include Inbound Server Addresses have an icon domain_icon.jpgbeside the domain name. When the MX records for the domain have been configured to include Inbound Server Addresses the icon disappears.
    2. Click the name of an existing policy in the Policy List. The Edit Policy screen appears displaying the Domain tab.
      The addresses display under the Inbound Server Addresses area of the Domain tab.
      Note
      Note
      The addresses differ depending on your geographic location and the choices you made during the installation process. Consult the documentation supplied by your DNS provider to make the changes. The process for making the modification is different depending on the DNS service your company uses.
  2. Configure the MX Records.
    Add the "Inbound Server Addresses" to the Mail Exchanger (MX) records in your DNS server, or your DNS provider.
    Tip
    Tip
    Trend Micro recommends configuring the MX records for Cloud Pre-Filter with a higher priority (specify a lower number) than your existing MX records. Your existing MX records then act as a backup to Cloud Pre-Filter.
    1. Continuing the example, configure the MX records on your DNS server as follows:
      example.com MX preference = 10, mail exchanger = example.com.eXXXX.gXXXX.ngXXXX.im.emailsecurity.trendmicro.com
      example.com MX preference = 10, mail exchanger = example.com.eXXXX.gXXXX.pgXXXX.im.emailsecurity.trendmicro.com
      example.com MX preference = 30, mail exchanger = mail01.your-domain.com
      your-domain.com MX preference = 30, mail exchanger = mail02.example.com
      mail01.example.com internet address = 1.1.1.1
      mail02.example.com internet address = 1.1.1.2
      After making the modifications to the MX records, Cloud Pre-Filter is the major point of entry for your domain. After the DNS record modifications take effect (up to 72 hours), all inbound email traffic is routed to Cloud Pre-Filter. Your original DNS record information is saved as a backup route.
    2. After the modifications take affect, test the message route by sending messages from another email service provider (Windows Live Hotmail or Gmail) to a recipient in your domain (for example your-domain.com). If you receive the message from the other email service provider, the DNS MX records are configured correctly.