What is a one-click unsubscribe (RFC 8058)?

Still have a question, spotted an error, or have a better explanation or a source we should cite?

One-click unsubscribe lets someone opt out of your emails with a single action, no landing page, no confirmation step, no "are you sure?" The unsubscribe happens automatically when they click, defined by RFC 8058.

It works through two email headers sent with every message: List-Unsubscribe and List-Unsubscribe-Post. The first tells mailbox providers where to send the unsubscribe request. The second signals that the unsubscribe should happen via a POST request (machine-to-machine) rather than requiring the recipient to click through to a web page.

Why this matters now

In early 2024, Gmail and Yahoo Mail made one-click unsubscribe mandatory for bulk senders. If you send more than 5,000 messages per day to Gmail addresses, you need both headers correctly implemented. Senders without them started seeing spam folder placement increases and delivery rate drops.

The reasoning is straightforward. If someone can't easily leave your list, the next option is the spam button. One-click unsubscribe keeps people off your complaint rate, not off your list (well, both eventually, but the complaint damage is worse).

Does your ESP handle this automatically?

Most major ESPs (Mailchimp, Klaviyo, Brevo, and others) add these headers automatically for qualifying accounts. But "automatic" doesn't always mean "correctly set up." If you've customized your sending domain, moved to a new ESP, or are using a custom SMTP setup, it's worth verifying the headers are there.

You can check your headers directly with our free Email Header Analyzer. Send yourself a test email, grab the raw headers, and paste them in. If List-Unsubscribe-Post is missing, that's your gap.

Contributors

Who worked on this answer

Every name links to their profile. Every company links to their site. Real people, real accountability.

Ask an AI · tailored to your setup

Check My One-Click Unsubscribe Setup

I just read the Email Almanac entry on one-click unsubscribe (RFC 8058). Help me verify my setup is compliant and fix any gaps before my next send. Walk me through: 1. How to check whether my emails are sending both List-Unsubscribe and List-Unsubscribe-Post headers 2. Whether my ESP handles this automatically or whether I need to configure it 3. What the deliverability impact looks like if I'm non-compliant with Gmail and Yahoo's 2024 requirements 4. How to test and confirm the unsubscribe works end-to-end --- My details (fill in what applies): - ESP or sending platform: Mailchimp / Klaviyo / Brevo / SendGrid / custom SMTP / other - Daily send volume to Gmail addresses: rough estimate - Whether I've checked my email headers before: yes / no - Recent delivery changes: spam folder placement, rate drops, throttling - Domain and DKIM status: set up / not sure

Edit the yellow boxes, then send to the AI of your choice.