Skip to content

/ Glossary — List & Compliance

What is one-click unsubscribe?

The standardized opt-out that lets recipients leave in a single action — now mandatory for bulk senders under Gmail and Yahoo's rules. Here's what it requires and why it helps you.

/ Definition

One-click unsubscribe is a standardized mechanism, defined in RFC 8058, that lets a recipient opt out of your mail in a single action directly from their mailbox — without being taken to a landing page or asked to log in. The mailbox provider shows a native unsubscribe option, and one click sends the opt-out request straight to the sender.

As of the bulk sender rules from Google and Yahoo, it's no longer optional: bulk senders must support one-click unsubscribe and honor opt-outs within two days. It requires specific list-unsubscribe headers in your mail, and the opt-out must be processed promptly by adding the recipient to your suppression list.

/ In practice

What it requires

Technically, one-click unsubscribe depends on two headers: a List-Unsubscribe header giving the opt-out method, and a List-Unsubscribe-Post header that signals support for the one-click standard so the provider can send the request without the recipient leaving their inbox. When a recipient clicks the native unsubscribe link, the provider sends a request to your endpoint, which must register the opt-out. The bulk sender rules require honoring it within two days, though processing it immediately is better practice and keeps your complaint rate down.

Why easy unsubscribe helps you

It can feel counterintuitive that making it easy to leave is good for you, but it is. The alternative to an easy unsubscribe isn't a retained subscriber — it's a frustrated recipient who marks you as spam, and a spam complaint damages your reputation far more than a quiet unsubscribe does. A recipient who no longer wants your mail will leave one way or another; a frictionless unsubscribe lets them go cleanly instead of hitting the spam button, which protects your standing with the mailbox providers.

/ Implementing it correctly

Headers, endpoint, and processing

Getting one-click unsubscribe right has three parts that all have to work together. The mail must carry both the List-Unsubscribe header and the List-Unsubscribe-Post header that signals RFC 8058 support, because providers only offer the native one-click option when both are present and correct. The unsubscribe URL must point to an endpoint that accepts the provider's automated POST request without requiring any human interaction — no confirmation page, no login. And the opt-out it receives must actually be processed, adding the recipient to your suppression list promptly, within the two-day window the rules require and ideally at once. A common failure is implementing the headers but pointing them at a landing page that expects a click, which breaks the one-click flow and can leave you non-compliant despite appearing to support it. The headers-pointing-at-a-landing-page mistake is common enough that it is worth testing the actual one-click flow from a real mailbox rather than assuming the presence of the headers means it works.

Easy to leave beats easy to complain. We implement it correctly.

We set up RFC 8058 one-click unsubscribe with proper headers and instant suppression, keeping you compliant and your complaint rate low. Bring us your sending.

Book infrastructure review