Mailchimp one-click unsubscribe: headers, body links, and validation

Mailchimp's two-click unsubscribe page for a link in an email body does not replace or disable header-based one-click unsubscribe. Mailchimp says the body or footer link opens a confirmation page to limit accidental opt-outs, while Gmail and Yahoo evaluate one-click capability from message headers. Send a safe test through the same Mailchimp campaign path and inspect its raw source before treating the requirement as met.

Who is affected?

This page is for Mailchimp operators sending marketing campaigns to Gmail or Yahoo recipients. Mailchimp's About Unsubscribes documentation requires an unsubscribe method in its email campaigns and explains that its body-link confirmation step is intended to reduce accidental unsubscribes caused by bot or filter clicks. That documented body-link behavior is distinct from the source-code headers used for the provider-controlled one-click process.

The recipient's mailbox decides whether to show an unsubscribe control. You should keep Mailchimp's visible link in the message and verify the headers in a received copy. If the question is how the RFC header pair and endpoint work, use the vendor-neutral one-click unsubscribe guide. If you are reviewing the wider provider checklist, see sender requirements.

Unsubscribe evidence is separate from domain authentication and inbox placement. The Mailchimp SPF and DKIM setup guide covers authentication records, while the Mailchimp spam-placement guide covers a different recipient-side outcome.

What are the requirements?

Mailchimp's body link is a separate path

Mailchimp says a subscribed contact who selects the unsubscribe link in a marketing email's body or footer reaches an unsubscribe page and must select unsubscribe again. Mailchimp also states that this two-click process does not affect the one-click unsubscribe process available through email headers, which Gmail and Yahoo require rather than a one-click body link. Mailchimp's unsubscribe guidance is the controlling source for that product-specific distinction.

Header-based one-click needs the RFC pair

RFC 8058 specifies a List-Unsubscribe field containing an HTTPS URI and a List-Unsubscribe-Post field containing List-Unsubscribe=One-Click. The RFC requires valid DKIM coverage for both fields. A mailbox provider may use that pair to perform an HTTPS POST to the listed URI after its recipient chooses the provider's control. Mailchimp's body-link confirmation page neither proves nor disproves that those headers were included in a particular campaign.

List-Unsubscribe: <https://unsubscribe.example.invalid/token/opaque-value>
List-Unsubscribe-Post: List-Unsubscribe=One-Click

This is an illustrative RFC-shaped header pair, not a Mailchimp value to copy. The delivered message is the evidence for the actual sending path.

Google's scope still includes a visible link

Google's email sender guidelines apply one-click unsubscribe to marketing and subscribed messages from senders that deliver more than 5,000 messages per day to personal Gmail accounts. Those covered messages must also include a clearly visible unsubscribe link in the message body. The header capability and the body link therefore serve separate requirements, even when they both lead to an opt-out.

When does the requirement take effect?

Google lists February 1, 2024 as the effective date for its bulk-sender requirements. The relevant current scope is the sender's daily volume to personal Gmail accounts and the message type, not whether Mailchimp's body link needs a confirmation click. Recheck Google's live sender guidelines if campaign volume, recipient mix, or provider policy changes.

Mailchimp's cited documentation does not state that every campaign path always emits an RFC 8058 header pair. Treat a raw message from the same account, campaign type, From identity, and audience path as the test evidence. Mailchimp Transactional is a separate product with its own outbound-email documentation, so do not use transactional documentation as proof of a Marketing campaign's headers.

How do I implement the requirement?

1. Keep the Mailchimp body unsubscribe link

Use Mailchimp's required unsubscribe mechanism in the campaign body or footer. Do not remove it because a mailbox might offer a header-based control. Mailchimp documents the body link as the platform's unsubscribe process, and Google separately requires a visible link for covered bulk marketing and subscribed messages.

2. Send a safe campaign-path test

Send a test through the exact Mailchimp product, campaign type, From identity, and authenticated domain you use in production. Address it to a mailbox you control and do not trigger an opt-out against a customer address. This test is needed because a campaign's actual source, rather than the visual editor or body link, establishes which headers were emitted.

3. Escalate missing or unclear header evidence to Mailchimp support

If the raw source lacks either RFC 8058 header, preserve the test headers and campaign context before contacting Mailchimp support. Do not add a self-hosted unsubscribe endpoint or hand-edit a campaign as a workaround unless Mailchimp documents that option for the exact product path. A different path could create an inconsistent suppression process.

How do I validate compliance?

Open the received message's original source and look for List-Unsubscribe and List-Unsubscribe-Post: List-Unsubscribe=One-Click. For an RFC 8058 implementation, the first field needs an HTTPS URI and the second has the exact one-click value. Also check the DKIM signature's h= list for both header names, as RFC 8058 requires. Keep the headers as evidence, but do not publish recipient-specific URLs or tokens.

Then verify the limits of that result. A test source can show whether Mailchimp emitted the relevant header pair. It cannot prove that Gmail, Yahoo, or another mailbox will render a specific control, that the provider's POST succeeded, or that all audience and suppression records updated. Keep the body link available and investigate any recipient-specific unsubscribe result through the authorized account workflow.

Continue the provider-requirement review

After you capture the campaign headers, use the Gmail and Yahoo sender requirements checklist to review the remaining sender requirements. That checklist does not inspect a private Mailchimp account, a received message, endpoint response, or audience state, so retain the raw-message evidence from this test.