InterScanTM Messaging Security Virtual Appliance - Online Help ...

Verifying Cloud Pre-Filter Works
You can verify that a policy works correctly before activating the policy.
Example
Configuring Cloud Pre-Filter
You want to verify that a policy created for the domain your-domain.com processes
your email traffic correctly and that Cloud Pre-Filter directs your email messages to your
IMSVA. To verify the policy works correctly, send an email message with a specified
sender and recipient account (the recipient’s domain should be part of
your-domain.com) directly to the Cloud Pre-Filter inbound server for
your-domain.com. The example Cloud Pre-Filter inbound server addresses for the
policy are prefilter.in.eu01.emsp.trendmicro.eu and
prefilter.in.eu02.emsp.trendmicro.eu. Send the test email message to either
inbound server address. Wait a few minutes after sending the email message and query
the message tracking logs using Cloud Pre-Filter + IMSVA data.
Note: The test email message must be sent directly to the Cloud Pre-Filter inbound server
for the domain. The Cloud Pre-Filter inbound server addresses for the domain appear
on the Domain tab for the policy.
Configuring DNS MX Records
After configuring Cloud Pre-Filter settings and verifying that email message traffic is
delivered from Cloud Pre-Filter to IMSVA, add the Cloud Pre-Filter "Inbound Server
Addresses" to the MX records for your DNS server. This is final step before using
Cloud Pre-Filter to scan your email message traffic.
WARNING! You MUST configure your mail delivery (MX) records to route your email
message traffic through Cloud Pre-Filter. If this step is not completed,
your email messages will be delivered to your local servers, and not to
Cloud Pre-Filter for scanning.
8-13