How one-click unsubscribe works

What actually happens on a send

Every campaign, reflector post, and digest that goes out for a list carries a List-Unsubscribe header pointing at a one-click unsubscribe link, plus List-Unsubscribe-Post so a compliant mail client (Gmail, Outlook, Apple Mail) can send the unsubscribe as a background request without the recipient leaving their inbox. A visible unsubscribe link also appears in the message footer for clients that don't support the header.

Scoped to the list, not the account

Clicking unsubscribe — or a mail client actioning the header automatically — removes the recipient from that one list only. If they're subscribed to other lists on the same account, those are untouched. This matters for organisations running several lists at once (a branch list, a committee list, a regional list): leaving one shouldn't silently drop someone from the rest.

The one exception is global suppression — a hard bounce or a spam complaint suppresses that address account- wide, on every list, since continuing to send to a bounced or complaining address damages deliverability for everyone else on the account.

No token database to run

The unsubscribe link is a stateless, signed token — verifiable without a database lookup, so there's no separate token table to provision, back up, or leak. This is also why rotating account credentials never breaks an unsubscribe link already sitting in a message someone received months ago.

The confirmation step

The one-click header path is silent, by design — that's what makes it usable directly from a mail client's UI. Clicking the visible footer link instead shows a small confirmation page, so a recipient who clicks through from their inbox gets a clear signal that the unsubscribe took effect.

Related

See how reflector lists work for how digest frequency and unsubscribe interact on discussion lists, or back to the getting-started guide.