# One-click unsubscribe

> A standards-based HTTPS mechanism that lets a mailbox provider submit an unsubscribe request without a login or confirmation page.

- **Category:** Audience
- **Updated:** July 2026
- **Canonical page:** [https://emailbump.com/glossary/one-click-unsubscribe](https://emailbump.com/glossary/one-click-unsubscribe)

## Definition

One-click unsubscribe uses List-Unsubscribe and List-Unsubscribe-Post headers as specified by RFC 8058. Supporting mailboxes can present a native unsubscribe control and send a POST request to the HTTPS URL.

It complements rather than replaces the clearly visible unsubscribe link in the message body. Google requires both for marketing and subscribed messages from senders above its bulk threshold.

## Why it matters

A simple exit gives recipients an alternative to the spam button and helps senders honor preference changes quickly. It also keeps unsubscribe behavior available when message HTML does not render as expected.

## How it works

1. The sender adds an HTTPS unsubscribe URL in List-Unsubscribe.
2. List-Unsubscribe-Post declares the one-click operation.
3. The relevant headers are covered by a valid DKIM signature.
4. The mailbox provider can POST the request and the sender suppresses future covered mail promptly.

## Example: RFC 8058 headers

```text
List-Unsubscribe: <https://email.example/unsubscribe/opaque-token>
List-Unsubscribe-Post: List-Unsubscribe=One-Click

The URL must identify the subscription safely without requiring a login.
```

## Common mistakes

- Using a GET request that unsubscribes when security scanners follow the link.
- Requiring login, password, or another confirmation after the one-click POST.
- Omitting the visible body unsubscribe link.
- Failing to DKIM-sign the list headers.

## Key takeaways

- One-click is a header-based POST flow.
- Keep a visible unsubscribe link in the body.
- Use opaque, scoped tokens and honor requests promptly.

## Related definitions

- [Suppression list](https://emailbump.com/glossary/suppression-list.md) — A durable do-not-send control containing recipients or destinations that must not receive certain email.
- [Spam complaint](https://emailbump.com/glossary/spam-complaint.md) — A recipient signal that a message is unwanted, usually created by marking it as spam or junk.
- [List hygiene](https://emailbump.com/glossary/list-hygiene.md) — The ongoing practice of keeping audience permission, reachability, source, and engagement data trustworthy.

## Related guides

- [What does unsubscribe mean in email?](https://emailbump.com/blog/what-does-unsubscribe-mean.md) — Learn what happens when you unsubscribe from email, what it does not delete or cancel, how it differs from blocking and reporting spam, and what senders must do next.
- [Why customers mark transactional email as spam—and how to stop it](https://emailbump.com/blog/reduce-transactional-email-spam-complaints.md) — An operational guide to expectation, message purpose, notification controls, duplicate prevention, form abuse, suppression, and complaint monitoring.
- [The email deliverability checklist for every campaign](https://emailbump.com/blog/email-deliverability-checklist.md) — A practical pre-send routine for protecting your sender reputation and reaching more inboxes.

## Primary sources

- [RFC 8058: One-click unsubscribe](https://www.rfc-editor.org/rfc/rfc8058)
- [Google: Email sender guidelines](https://support.google.com/mail/answer/81126?hl=en)