Using External MX Spam Filtering Services (SpamHero, MXGuarddog)

Created by Curtis Hammock, Modified on Sun, 15 Nov at 7:22 PM by Curtis Hammock

You can route your custom domain's incoming mail through an external third-party spam filtering gateway (such as MXGuarddog, SpamHero, or Antispamcloud) before it reaches Purelymail. The external service filters spam, viruses, and phishing, and then forwards clean mail to your Purelymail mailboxes.


How the Setup Works (Step-by-Step)

Setting up an external anti-spam service in front of Purelymail requires configuration in three places: Purelymail, your anti-spam provider, and your domain DNS.

1. Purelymail Setup

  • Ensure your custom domain is added and verified in the Account Admin portal under Domains.
  • Keep the domain delivery mode set to Purelymail (the default setting).
  • Create your user mailboxes and routing rules under Users and Routing.

2. Anti-Spam Provider Setup (Example: MXGuarddog / SpamHero)

  • Add your domain in your anti-spam provider's dashboard.
  • Set the Destination Mail Server (also called Target Server, Inbound Mail Host, or Delivery Host) to:

mailserver.purelymail.com (port 25).

  • If the provider asks to verify connectivity, allow it to run a connection test to mailserver.purelymail.com.
  • No Login or Password Required: Inbound mail delivery between servers runs over standard SMTP (port 25). The anti-spam service never needs, asks for, or uses your Purelymail login credentials or mailbox passwords. It only needs the destination hostname mailserver.purelymail.com.

3. Domain DNS Setup

  • Log into your domain registrar or DNS host (e.g. Cloudflare, Namecheap, GoDaddy).
  • Replace MX Records: Remove Purelymail's default MX record (mailserver.purelymail.com) and add your anti-spam provider's assigned MX servers instead (for example, MXGuarddog uses *.ik2.com mail servers).
  • Keep SPF and DKIM for Outbound Mail: Since your users still send outbound mail through Purelymail, leave Purelymail's SPF record (v=spf1 include:_spf.purelymail.com ~all) and DKIM CNAME records active in your DNS.

Why Upstream Filtering Relays Cause DMARC Issues

When an external anti-spam service relays mail to Purelymail:

  1. The incoming connection to Purelymail originates from the anti-spam provider's IP address rather than the original sender's server.
  2. If the original sender's domain has published a strict DMARC policy (p=reject), Purelymail checks whether the connecting IP is authorized in the sender's SPF record.
  3. Because the connecting IP belongs to the filtering relay, SPF fails. If the message also lacks a valid DKIM signature (or the relay modified the message headers), DMARC fails and the message would normally be rejected.

Built-In Whitelist for Known Services

To prevent legitimate forwarded mail from bouncing, Purelymail includes a built-in server whitelist that automatically skips DMARC reject enforcement when incoming mail arrives from verified relay hostnames:

  • MXGuarddog (*.ik2.com)
  • SpamHero (*.mxthunder.net)
  • Antispamcloud (*.antispamcloud.com)

If you use one of these three services, no special DMARC configuration is required on Purelymail.


What to Do If Using an Unlisted Anti-Spam Service

If you use an anti-spam gateway that is not listed above, its connecting IPs are not in Purelymail's built-in whitelist. If senders with strict DMARC policies have their mail rejected, you can disable DMARC reject enforcement on your account:

  1. Log into the Account Admin portal (purelymail.com/manage/login).
  2. Go to Account Settings and scroll down to DMARC Enforcement on Incoming Mail.
  3. Click Disable. When disabled, Purelymail will deliver incoming mail even if sender DMARC authentication fails due to upstream forwarding.

Still Need Help?

If you've followed these steps and are still running into trouble, check our Purelymail Support guide.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article