background

SpamExperts KnowledgebaseIncoming Filtering

Hosted Cloud MX records

To route the incoming email for your domain through the SpamExperts filtering cloud you have to change your MX records.

Prior to changing the MX records, it is best to check your TTL. We recommend a maximum value of “3600” in order to propagate any DNS changes faster. Higher TTLs can lead to spam not being filtered by our nodes yet.

Some DNS control panels require you to use a trailing dot (.) after the hostname. Please check with your DNS provider if this is the case for you.

Removal of old MX records is required to make sure all emails are filtered through the SpamExperts cloud, as spammers actively try different MX records (such as with the highest numbered priority) to bypass spam filters.

DNS changes may take some time before they are picked up by the DNS resolvers world-wide, so email may continue to deliver directly to the original MX records without filtering for 24 hours.

You can check using the SpamExperts log search or within the email headers if the message has passed through the SpamExperts filtering nodes.

Default MX records

Please edit the DNS settings for your domain:

  1. Ensure the domain has been added to the filtering system, next add the following MX records:
    • mx.spamexperts.com. (priority 10)
    • fallbackmx.spamexperts.eu. (priority 20)    
    • lastmx.spamexperts.net. (priority 30)
  2. Remove the original MX records

Private label MX records

Note: Usage of these records without a private label license leads to filtering automatically being suspended.

  1. Ensure the domain has been added to the filtering system, next add the following MX records:
    • filter10.antispamcloud.com. (priority 10) 
    • filter20.antispamcloud.com. (priority 20)
    • filter30.antispamcloud.com. (priority 30)
    • filter40.antispamcloud.com. (priority 40)
  2. Remove the original MX records

Private label EU/US-only MX records

Note: Usage of these records without a private label license leads to filtering automatically being suspended.

Note: For redundancy reasons we recommend to use our global records. Our uptime and service level guarantees do not apply to the EU/US-only records.

Note: GDPR does NOT require email to be routed via only a single geographical region.

  1. Ensure the domain has been added to the filtering system, next add the following MX records:
    • EU:
      • filter10-eu.antispamcloud.com. (priority 10)
      • filter20-eu.antispamcloud.com. (priority 20)
      • filter30-eu.antispamcloud.com. (priority 30)
      • filter40-eu.antispamcloud.com. (priority 40)
    • US:
      • filter10-us.antispamcloud.com. (priority 10)
      • filter20-us.antispamcloud.com. (priority 20)
      • filter30-us.antispamcloud.com. (priority 30)
      • filter40-us.antispamcloud.com. (priority 40)
  2. Remove the original MX records

Custom MX records

Custom MX records are not available for trial users on our Hosted Cloud. 1 set of custom MX records is available to clients with the (premium) Private Label feature.

To create your own MX-record hostnames, you need to setup 4 NS-record hostnames in your DNS pointing to our nameservers:

mx1.example.com. NS dns1.spamrl.com.
mx1.example.com. NS dns2.spamrl.com.
mx1.example.com. NS dns3.spamrl.com.
mx1.example.com. NS dns4.spamrl.com.
mx2.example.com. NS dns1.spamrl.com.
mx2.example.com. NS dns2.spamrl.com.
mx2.example.com. NS dns3.spamrl.com.
mx2.example.com. NS dns4.spamrl.com.
mx3.example.com. NS dns1.spamrl.com.
mx3.example.com. NS dns2.spamrl.com.
mx3.example.com. NS dns3.spamrl.com.
mx3.example.com. NS dns4.spamrl.com.
mx4.example.com. NS dns1.spamrl.com.
mx4.example.com. NS dns2.spamrl.com.
mx4.example.com. NS dns3.spamrl.com.
mx4.example.com. NS dns4.spamrl.com.

Before adding the MX records to your domain, please open a support ticket so that your hostnames will get added to the spamrl.com nameservers, as they will only function once we create them at our end. Only 1 set of custom MX-record hostnames is allowed per client. The domain that you want to apply filtering to then can use your personal MX records as follows:

yourdomain.ext. MX 10 mx1.example.com.
yourdomain.ext. MX 20 mx2.example.com.
yourdomain.ext. MX 30 mx3.example.com.
yourdomain.ext. MX 40 mx4.example.com.

Some DNS control panels do not require you to use a trailing dot (.) after the hostname. Please check with your DNS provider if this is the case for you.

As CNAME hostnames are not supported for MX record hostnames, you can alternatively use an ALIAS DNS record pointing to your custom MX-record hostname in case you need more than 1 set of MX-record hostnames.


Was this article helpful?

Related articles

Search result for :