1. Check your address lists

Review, modify, and save your address list for each of your domains.

In the portal, click Services > Email Services > Platform.

Add your list of valid email addresses to ensure that you only receive email for legitimate users in each domain in your organization. Email Security.cloud drops any emails that are sent to addresses on your domain that are not registered for your organization.

You can manage this list yourself in the portal or use the Synchronization Tool .

2. Review your inbound and your outbound routes for email traffic

Review your inbound and your outbound email routes for your domains.

In the portal, click Services > Email Services > Inbound routes and Outbound routes.

3. Check your service configuration settings

When Email Services are fully deployed, the AntiVirus service is automatically active and the AntiSpam service may be enabled with default settings. Your inbound email (and outbound email, if provisioned) automatically passes through the cloud security service scanners. To customize the settings for AntiVirus and AntiSpam, make the necessary configuration changes before you change your MX records.

In the portal, click Services > Email Services.

4. Setting up Spam Quarantine

Spam Quarantine enables your organization's users to view the emails that the Email AntiSpam service has detected as spam. These emails are viewable in a portal called Spam Manager.

If you have Spam Quarantine enabled, Quarantine the mail is an action in your Email AntiSpam Detection Settings page of the portal. If this action is not enabled and you want it to be, refer to your confirmation email for contact details.

For Spam Quarantine, you must have Address Registration enabled and active.

The URL for Spam Manager is:

https://spammanager-4.messagelabs.com/login.xsp

5. Redirect your inbound email traffic to the Symantec.cloud infrastructure.

Complete the following MX record changes within five working days of receiving your confirmation email.

It may take up to 24 hours for MX record changes to result in full propagation.

Make sure that any previous MX records in place are NOT removed until the change to Symantec.cloud has fully propagated. When the records are propagated, ensure that there are no back-up MX records left in place.

If an external organization (e.g. your ISP) manages your MX records, ensure that this information is passed on to them.

6. Redirect your outbound mail traffic (optional)

Configure your organization's SMTP server to have your outbound email scanned. Use your assigned cluster host name rather than a single IP to ensure security and resiliency as follows:

7. Restrict SMTP traffic

We recommend that you lock down port 25 SMTP traffic to and from your Internet gateway to the following IP ranges:

Symantec.cloud IP Ranges

Locking down port 25 prevents spam and viruses being sent directly to or from your mail server. It also enables us to balance traffic across the infrastructure if Internet conditions require it. For example, during mass mailer outbreaks, dictionary attacks, and denial-of-service attacks.