Skip to content
  • There are no suggestions because the search field is empty.

Mailchimp SPF, DKIM and DMARC setup

To pass DMARC on mail you send through Mailchimp, authenticate your own domain in Mailchimp so it signs your campaigns with DKIM as that domain. Then publish one DMARC record at your DNS host, starting at p=none with reports switched on, and only tighten the policy once the reports show Mailchimp passing with alignment. SPF isn't the route here: Mailchimp's marketing mail aligns through DKIM.

This guide covers Mailchimp's marketing product, the one you use for campaigns. Mailchimp Transactional works differently and has its own short section further down.

What happens before you authenticate

You can pick a From address on your own domain, say news@example.com, without authenticating anything. Until you authenticate the domain, though, Mailchimp signs that mail as itself. The envelope sender (the Return-Path) uses a Mailchimp domain such as mcsv.net, mcdlv.net, mailchimpapp.net or rsgsv.net. Some inboxes then show "via" or "on behalf of" that domain next to your name. Most stop once the domain is authenticated, though some, Outlook among them, may still show that a sending service was involved.

That's a problem for DMARC. DMARC passes when SPF or DKIM passes and the domain that passed lines up with your From domain (Identifier alignment for SPF and DKIM). Before authentication, there's no DKIM signature with d=example.com, and SPF is checked against the Mailchimp envelope domain, so neither aligns. At p=none that only shows up in reports. At p=quarantine or p=reject, receivers can filter or refuse that mail (What happens to failing mail under each policy).

One limit first: you can't authenticate a free mailbox address such as a Gmail or Yahoo address. Send from a domain you own. Free mailbox addresses can't be used for BIMI either.

Mailchimp domain authentication (this is the DKIM step)

Authentication is what makes DMARC pass for Mailchimp mail. Mailchimp offers an automatic setup, which may ask you to sign in to your DNS host, and a manual setup where you add the records yourself.

The domain has to be verified first, usually through a link or code sent to an address on that domain. Then, in your account settings, open the Domains page and choose Start authentication next to the verified domain.

For a manual setup, you add two CNAME records for DKIM. Copy the Name (host) and Value for each one from your Mailchimp account, exactly as shown. Don't copy them from another domain or from an old guide. They aren't fixed values you can look up somewhere else.

Three things trip people up:

  • The doubled name. Many DNS hosts add your domain to whatever you type in the Name field. If Mailchimp shows k2._domainkey.example.com and you paste all of it, you can end up with k2._domainkey.example.com.example.com. Enter only the relative part, k2._domainkey in this example, then check the full name your DNS host saved.
  • Cloudflare's proxy. If your DNS is on Cloudflare, set both CNAMEs to DNS-only and keep CNAME flattening off for them, so receivers see the CNAME itself. Details are in Add SPF, DKIM and DMARC records in Cloudflare DNS Add SPF, DKIM and DMARC records in Cloudflare DNS.
  • Patience. Most records validate within a few minutes, but it can take up to 48 hours. The domain then shows as Authenticated.

If you change the CNAME records later, disable authentication on the Domains page first, then authenticate again.

"Authenticated" in Mailchimp means the records resolve. It doesn't prove your mail passes DMARC. That's what the reports are for.

SPF and the Return-Path

You don't add a Mailchimp include to your SPF record for marketing mail. The marketing setup doesn't ask for one, and we haven't found a custom Return-Path option for marketing mail. The envelope sender stays on a Mailchimp domain, so SPF won't align for this mail however you write your record. That's normal, and it isn't a problem as long as DKIM aligns. The two routes are compared in SPF include vs DKIM from the vendor.

You still need one SPF record on your From domain for your other senders, such as your mailbox platform. If you use Google Workspace and Mailchimp, for example, the SPF record stays as it was:

example.com.  TXT  "v=spf1 include:_spf.google.com ~all"

Don't create a second SPF record "for Mailchimp". Two SPF records make SPF fail with a permanent error for everything on the domain (Two SPF records). If Mailchimp ever asks for an include in your account, add it to the existing record and keep an eye on the 10-lookup limit (The 10-lookup limit and SPF permerror).

Mailchimp Transactional

Mailchimp Transactional (for receipts, password resets and other app mail) has its own records and an option the marketing product doesn't have.

  • DKIM: two CNAMEs. mte1._domainkey.example.com points to dkim1.mandrillapp.com, and mte2._domainkey.example.com points to dkim2.mandrillapp.com. Enter the relative names if your DNS host appends the domain.
  • DMARC first: Transactional won't send to external recipients until the domain has DKIM and a valid DMARC policy.
  • Custom Return-Path: this one exists. Point a subdomain (not the root domain) at mandrillapp.com with a CNAME, for example mail.example.com, then add that subdomain in Transactional's tracking and return-path settings. You can apply it to all mail or per message, and Transactional still handles bounces. With it in place, SPF can align as well as DKIM.

Keep the two products apart when you read your setup. The Transactional Return-Path doesn't carry over to campaigns.

Your DMARC record

DMARC is a TXT record at _dmarc.example.com, published at your DNS host. It's not a setting inside Mailchimp.

Mailchimp's authentication steps also ask you to add a DMARC record. If you don't have one yet, a safe starting point is a monitoring policy with reports:

_dmarc.example.com.  TXT  "v=DMARC1; p=none; rua=mailto:dmarc-reports@example.com"

Use the reporting address our platform gives you in rua, not the example above. What each tag does is in DMARC tags explained: p, sp, np, adkim, aspf, rua, ruf, fo, and t, report addresses and authorization in rua, ruf, and report authorization, and the full record walk-through on our DMARC setup page.

If you already have a DMARC record, keep it. Don't add a second _dmarc TXT, because receivers ignore a domain's DMARC records when there's more than one. Don't let a setup step swap your existing policy or your rua for a sample record either. If you're already at enforcement, that would quietly take you back to p=none.

Check the reports before you change anything

Once the domain shows as Authenticated, send a real campaign, even a small one to your own team, and look at two things.

The message header. In the Authentication-Results header of a received copy, you want dkim=pass with header.d=example.com and dmarc=pass. Any SPF result will be for a Mailchimp domain, which doesn't count toward DMARC alignment. The full test is step 6 in How to add a third-party sender without breaking DMARC.

Your aggregate reports. Over the next few days, Mailchimp should appear as a source with DKIM passing and aligned to your domain at several receivers. SPF failing alignment on that source is expected for marketing mail. On its own, it doesn't make the mail fail DMARC, as long as aligned DKIM passes. In our reporting, each sending source has its own view, so Mailchimp's results sit apart from your mailbox platform's.

If Mailchimp mail shows DKIM failing or not aligned, fix that before you go further. Third-party mail fails alignment walks through it.

Moving to enforcement

Move to p=quarantine, then p=reject, one domain at a time, and only after the reports show Mailchimp and every other legitimate source passing with alignment (A safe rollout: p=none to quarantine to reject, When you are ready for p=quarantine, When you are ready for p=reject). Mailchimp is rarely the only sender on a domain. Invoices, help desk replies and staff mailboxes need to pass too. If marketing sits on the same domain as mail customers depend on, consider a sending subdomain (Shared domains and multi-service setups).

Don't authenticate and enforce in the same sitting. Give the reports at least one full sending cycle first.

Showing your logo (BIMI) after enforcement

BIMI is a DNS record on your domain, not a Mailchimp setting. Mailchimp's part is to keep signing your campaigns with aligned DKIM. The rest happens on the domain, and only once DMARC is at enforcement (p=quarantine or p=reject).

You'll need your logo as an SVG Tiny PS file hosted over HTTPS (SVG Tiny PS logo requirements). Gmail also requires a VMC or a CMC before it shows the logo, while Yahoo doesn't require a certificate. Display is always up to the mailbox provider. A CMC can be based on prior use: the logo has appeared on your own website for at least 12 months, which is checked through the Internet Archive. The official requirements list other routes as well. A VMC is based on a registered trademark; see VMC certificate, and for choosing between them, is a VMC still worth it now that CMC exists.

For the Mailchimp side of the story, read BIMI and Mailchimp. The requirements are in BIMI requirements checklist, the move from enforcement to BIMI in How to move from DMARC enforcement to BIMI, why DMARC comes first in What is BIMI, and why DMARC comes first, and what to check when the logo doesn't appear in Why your BIMI logo is not showing.

Free DMARC account

Not sure which sender is failing?

Connect your domain's DMARC reports and see every service that sends as your domain, and whether each one passes SPF, DKIM and DMARC.

  • Every sending source in one dashboard
  • SPF, DKIM and alignment results per sender
  • No XML files to read

Create a free DMARC accountTalk to an expert

FAQ

Do I need an SPF include for Mailchimp?

Not for marketing campaigns. Mailchimp's marketing mail aligns through DKIM, so keep one SPF record for your other senders and don't add a second one.

Is a custom Return-Path only on enterprise plans?

We haven't found a custom Return-Path in Mailchimp's marketing setup, and we can't confirm that any plan adds one, so don't plan around it. Mailchimp Transactional does offer one, by pointing a subdomain at it with a CNAME. Either way, DMARC can pass on aligned DKIM without SPF alignment.

Mailchimp says the domain is Authenticated. Does DMARC pass?

Not automatically. Authenticated means the records resolve. Check your aggregate reports for Mailchimp passing DKIM with alignment to your domain.

Mailchimp asked me to add a DMARC record, and I already have one. What do I do?

Keep the record you have. Don't add a second _dmarc TXT, and keep rua on the reporting address our platform gives you.

Why does SPF fail for Mailchimp in my reports?

Usually because the envelope sender is still a Mailchimp domain, which is expected for marketing mail. Check DKIM alignment for that source before you change anything.

Mailchimp domain authentication isn't working. What should I check?

That the domain was verified first, that each CNAME name wasn't doubled by your DNS host, that the CNAMEs aren't proxied or flattened if you're on Cloudflare, and that you've allowed up to 48 hours. If you edited the records after authenticating, disable authentication and start again.