Mailchimp is the default email platform for hundreds of thousands of small senders, and for the most part it does its job well. But when campaigns start landing in Spam, the cause is rarely generic — it is almost always one of four Mailchimp-specific failure modes. This article walks through each one, the setting that fixes it, and the point at which Mailchimp stops being the right tool.
If your Mailchimp opens fell off a cliff, check three things in order: (1) is your custom domain authenticated in Mailchimp's Sending Domains panel, (2) does your From header still show via mailchimp.com, and (3) what is the reputation of your assigned shared IP pool. Most Mailchimp Spam problems are one of these.
The four Mailchimp-specific failure modes
Mailchimp's architecture is different from a self-hosted MTA or a developer-oriented ESP like Postmark or SendGrid. Those differences create a predictable set of deliverability traps.
1. Shared sending pool reputation
By default every Mailchimp sender — free tier, Essentials, Standard — shares an IP pool with thousands of other accounts. When a pool neighbour gets reported for sending unsolicited mail, Spamhaus and the major ISPs can throttle the entire pool for hours. Your content is fine, your auth is fine, but your Monday morning newsletter still lands in Promotions or Spam.
2. The "via mailchimp.com" header
When a domain is not fully authenticated, Gmail adds a via mailchimp.com note next to your sender name. That tag kills trust instantly — recipients read it as "this isn't really from my bank, it is from some bulk tool" — and Gmail itself weighs the signal negatively for inbox placement.
3. Free-tier and low-volume domain authentication
On the free tier, Mailchimp historically used its own domain to sign DKIM and cover SPF. This is still the case for senders who haven't clicked through the "Verify domain" flow in Audience settings. Good for Mailchimp's infrastructure; bad for your domain's long-term reputation, since you never build one.
4. The default tracking domain
Every click in a Mailchimp campaign is wrapped through list-manage.com. That host is enormous and shared across all Mailchimp customers, which means a single bad actor can tank its reputation for a window. Gmail's filter looks at click-host reputation alongside sender reputation; a poisoned tracking host drags your message down.
Authenticate your own domain in Mailchimp
This is the single biggest change you can make. Mailchimp calls it "domain authentication" but it is just standard DKIM and SPF on a domain you control.
- Open Audience → Settings → Domains. Click Add & verify domain.
- Enter the domain on your From address (e.g.
yourbrand.com). Mailchimp will email you a verification link. - After verification, click Authenticate domain. Mailchimp gives you two CNAME records to add:
k1._domainkey.yourbrand.comandk2._domainkey.yourbrand.com. - Publish the CNAMEs at your DNS host (Cloudflare, Route53, GoDaddy). Wait 10–60 minutes, then click Authenticate in Mailchimp.
- Check your SPF record. If you already have one, add
include:servers.mcsv.net. If you don't, publishv=spf1 include:servers.mcsv.net ~all.
Once authentication completes, Gmail stops showing via mailchimp.com, and DKIM is signed by your domain rather than mailchimpapp.net. Both are requirements for DMARC alignment — without them, a DMARC record at p=quarantine will silently fail half your sends.
Why "via mailchimp.com" appears and how to remove it
Gmail adds the via tag when the DKIM-signing domain doesn't match the visible From domain. The fix is the authentication flow above — specifically the two DKIM CNAMEs. If you authenticated long ago but the tag still appears, one of three things is wrong:
- CNAMEs were published but then removed during a DNS migration. Republish them.
- You are sending from a subdomain (
news.yourbrand.com) but authenticated the root. Add the subdomain separately in Mailchimp. - You use a From address on a different domain than your verified sending domain. Mailchimp falls back to its own signing domain.
After sending yourself a test campaign, open the message in Gmail, click the three dots → Show original. Look for the Authentication-Results header. You want dkim=pass header.d=yourbrand.com, not header.d=mailchimpapp.net.
When to move from shared to dedicated IP addon
Mailchimp offers a dedicated IP addon on Standard and Premium plans. It is not a universal fix — a dedicated IP with low volume can actually be worse, because you have no established reputation and no pool to hide inside. The rule of thumb: dedicated IP makes sense when you are sending over roughly 100,000 emails per month to engaged recipients, consistently, week after week. Below that, stay on the shared pool and focus on list hygiene.
If you are over the volume threshold and the shared pool is your problem, the dedicated IP addon runs around $30/month and requires a fresh warm-up — start at 5% of your normal volume and scale over two weeks. Skip the warm-up and you swap one reputation problem for another.
Reading Mailchimp's own deliverability report
Mailchimp's per-campaign report includes an Opens by domain section. This is the most useful deliverability signal Mailchimp gives you without paying for an external tool. What to look for:
- Gmail open rate dramatically lower than Outlook open rate. Usually means Gmail is routing you to Promotions or Spam. Check authentication and your content tone.
- Yahoo open rate near zero. Yahoo is aggressive with the 2024 bulk-sender rules. Confirm your DMARC record and
List-Unsubscribe-Postheader. - Apple / iCloud artificially high. Apple MPP pre-fetches images regardless of placement; a high Apple open rate does not prove inbox placement.
Diagnosing campaign by campaign
If one campaign performs and the next doesn't, the variable is probably content or list segment — not infrastructure. Open both campaign reports side by side and compare:
- Same audience segment, or different?
- Same From name and From address?
- Subject line length, emoji count, ALL CAPS words?
- Links in the body — any new tracking host, any new redirect?
- Time of day and day of week?
Most of the time a single variable explains the gap. Send the underperforming campaign through a placement test before the rebuild — you will know within three minutes whether it was a content problem, an authentication problem, or a pool problem.
When to jump ship
Mailchimp stops making sense at two distinct thresholds:
- Below 2,000 contacts — if you are under the free-tier cap and shared-pool reputation keeps hurting you, a dirt-cheap alternative like Buttondown or even plain Postmark with a simple template script will outperform.
- Above 100,000 contacts — Mailchimp's pricing scales aggressively here and the shared pool becomes a liability. A migration to Klaviyo (for e-commerce), Customer.io (for product), or SendGrid Marketing Campaigns with a dedicated IP becomes cheaper per message and gives you more control over reputation.
Before moving platforms, run a placement test on your current Mailchimp setup and again on the new platform's default setup. If the inbox rate is the same, the problem was you, not Mailchimp, and a migration won't fix it. Authenticate first, migrate second.