If you make use of a third party filtering service for inbound email filtering, your MX records will need to be set up in a specific way. This article is specifically for customers who are using a third party filtering service. If you use a third party service for hosting your email (not just filtering email) please see our article How to Modify your MX Records for instructions on how to properly set up your MX records.

If you do not already have the MX records for your third party filtering service, please contact them for these records. Many providers may also make this information available online either in a FAQ or set up documentation for the service. To illustrate this concept, we'll use a test domain (whhsupport.com) and example system numbers similar to what you would have if you were using Google's Postini email filtering service:

whhsupport.com.s7a1.psmtp.com
whhsupport.com.s7a2.psmtp.com
whhsupport.com.s7b1.psmtp.com
whhsupport.com.s7b2.psmtp.com

Begin by logging into your cPanel account.

Click on the "MX Entry" icon under the "Mail" area of your cPanel home screen.

In the MX Entry Maintenance screen, if you have more than one domain or subdomain, select the domain or subdomain you are changing the MX records for.

Before adding your new MX records, click the "Delete" link under the Actions column beside any existing MX records. Your email will not work properly if there are conflicting MX records.

Under the "Add New Record" area enter each record and it's priority. Click the "Add New Record" button to save the new MX record.

Please note, we are assigning priorites that Google recommends for Postini. If you are using a different email filtering service, please be sure to follow their instructions for the priority to be set for each record.

Once you have entered each of your new MX records, under the "Email Routing" area select "Local Mail Exchanger" and click the "Change" button to save your changes. We are choosing "Local Mail Exchanger" instead of Automatically Detect or Remote because the email needs to still be delivered to the Web Hosting Hub server after it passes through the third party filtering service.