Topic · Compliance
RFC 8058 one-click unsubscribe
RFC 8058 defines a standards-based way for compatible email clients to trigger a one-click unsubscribe from list messages.
How it works
A signed message supplies a List-Unsubscribe HTTPS URL and the List-Unsubscribe-Post header for a POST action.
What can go wrong
A normal unsubscribe page link alone is not equivalent to implementing the one-click protocol.
What to check or do
Check the required headers, DKIM coverage, endpoint response and end-to-end handling for eligible messages.
Practical scenario
A newsletter has a visible unsubscribe link, yet a mailbox provider flags missing one-click unsubscribe support. The HTML link may open a web page but does not satisfy the signed List-Unsubscribe-Post and HTTPS POST workflow.
Verification checklist
- Inspect List-Unsubscribe and List-Unsubscribe-Post in a delivered message.
- Confirm required headers are covered by a valid DKIM signature.
- Test HTTPS POST processing without requiring login or a web-form visit.
- Verify suppression is applied promptly across all marketing sending systems.
How to investigate RFC 8058 one-click unsubscribe
- Signal to investigate
- A sender publishes the header but its endpoint rejects a POST without a browser session.
- Evidence to collect
- Send a controlled request using the documented form body and verify suppression behavior.
- Common wrong conclusion
- Protect against unintended requests while implementing the standard; do not require sign-in to unsubscribe.
List-Unsubscribe: <https://example.com/unsubscribe/TOKEN>
List-Unsubscribe-Post: List-Unsubscribe=One-ClickEducational example; not validated against your live infrastructure.Put this into practice
Run a focused check, then explore protection if your domain needs it.