Mailchimp's help pages tie a legacy checklist to a 2024 threshold

The revenue mechanism

Mailchimp is one of the longest-running email marketing platforms still serving independent publishers, and its own help documentation is the layer where a general statute and a mailbox provider's specific technical rule meet in language a non-technical sender can act on. Mailchimp's anti-spam requirements article states directly that every email sent through the platform must comply with the US CAN-SPAM Act, applying that requirement even to accounts based outside the United States. Separately, its domain authentication article is where the platform states the newer, mailbox-provider-specific rule: Gmail and Yahoo require a published DMARC record from anyone sending more than 5,000 emails to their addresses in a 24-hour period.

What the documents show

The anti-spam article requires a physical mailing address or PO box in every promotional email and an unsubscribe link in every campaign, and it states Mailchimp itself provides a merge tag to insert that link automatically. The domain authentication article describes DKIM as protecting senders and recipients from spam, forgery and phishing, describes DMARC as a way to show a message genuinely comes from the claimed sender, and states the setup requires two CNAME records for DKIM and one TXT record for DMARC. It repeats the 5,000-message threshold in Mailchimp's own words, tying the platform's authentication instructions directly to the external requirement rather than describing it as Mailchimp's own invented rule.

The assumptions exposed

The two articles cover different layers and should not be read as one combined compliance certificate. Meeting the anti-spam article's requirements addresses a general US statute; meeting the domain authentication article's requirements addresses a specific pair of mailbox providers' technical thresholds. A sender could satisfy one and not the other, and Mailchimp's own text does not claim that completing its authentication wizard guarantees CAN-SPAM compliance, or that CAN-SPAM compliance satisfies Gmail or Yahoo's authentication requirement. Mailchimp also does not publish, on either page, its own aggregate figures for how many customer domains meet the 5,000-message threshold or how the platform enforces the requirement internally.

What to check before you rely on it

This is an editorial checklist drawn from Mailchimp's own stated instructions. A publisher should confirm the merge tag generating the unsubscribe link is actually present in every template used, not only the default one, and should verify the DKIM and DMARC records were completed, not merely started, in the domain authentication flow.

• Does every template in active use include the physical address and unsubscribe merge tags?
• Have the DKIM and DMARC DNS records been confirmed as verified inside the account, not left pending?
• Is daily sending volume to Gmail or Yahoo addresses tracked against the 5,000-message threshold?

Mailchimp's documentation is a reliable statement of what the platform asks a sender to configure; it is not itself a guarantee that either the statute or the mailbox providers consider that sender fully compliant.