Topic · Compliance
One-click unsubscribe
One-click unsubscribe allows recipients to leave subscribed marketing lists through a machine-readable mechanism.
How it works
RFC 8058 uses List-Unsubscribe and List-Unsubscribe-Post headers with a supported endpoint.
What can go wrong
A footer unsubscribe link alone may not satisfy one-click requirements for applicable bulk mail.
What to check or do
Implement authenticated unsubscribe handling and test with mailbox providers.
Practical scenario
A bulk sender includes an unsubscribe URL that opens a page asking users to log in and confirm again. This may satisfy neither the intended one-click user experience nor the provider’s applicable one-click header requirement.
Verification checklist
- Inspect List-Unsubscribe and List-Unsubscribe-Post headers in a delivered message.
- Verify the HTTPS endpoint handles the appropriate POST request securely.
- Confirm suppression propagates across all sending systems promptly.
- Keep the body unsubscribe method accessible alongside standardized headers.
How to investigate One-click unsubscribe
- Signal to investigate
- A promotional message provides only a click-through preference page and no RFC 8058 mechanism.
- Evidence to collect
- Inspect delivered List-Unsubscribe and List-Unsubscribe-Post headers and test the HTTPS POST endpoint.
- Common wrong conclusion
- A mailto URL or confirmation form alone is not the same as RFC 8058 one-click behavior.
How to interpret the evidence
One-click unsubscribe under RFC 8058 is a defined header and HTTPS POST workflow, not merely a footer URL that opens a preferences page. Providers impose requirements on specific types and volumes of marketing/subscribed mail. User-consent obligations and additional body links may apply separately under policy or law.
What to change and how to verify it
Inspect a delivered promotional message's List-Unsubscribe and List-Unsubscribe-Post headers, send a controlled test to the HTTPS endpoint and confirm suppression across all services. Check the relevant mailbox provider's current published sender policy before asserting compliance.
List-Unsubscribe: <https://example.com/unsubscribe/TOKEN>
List-Unsubscribe-Post: List-Unsubscribe=One-ClickEducational example; not validated against your live infrastructure.List-Unsubscribe-Post: List-Unsubscribe=One-ClickPut this into practice
Run a focused check, then explore protection if your domain needs it.