One‑Click unsubscribe (RFC 8058) — practical guide
Gmail/Yahoo bulk sender rules expect a frictionless, one‑click unsubscribe. This page shows a minimal, secure implementation and how to verify compliance without triggering live endpoints.
Add the headers
Add both headers and keep the HTTPS endpoint simple and idempotent.
Required headers
List-Unsubscribe: <mailto:unsubscribe@example.com>, <https://example.com/u/12345>
List-Unsubscribe-Post: List-Unsubscribe=One-ClickList-Unsubscribemay include bothmailto:andhttps:List-Unsubscribe-Postmust beList-Unsubscribe=One-Clickexactly
Security guardrails
- Never auto‑request unsubscribe URLs in background jobs
- Allow only
https://scheme; blockfile://,gopher://,http://169.254… - Short‑lived tokens bound to user and list; rate‑limit and log
- Return 200 on success without extra clicks; support CORS for in‑client handling
Verify and document
Our audit only checks presence/syntax (never dereferences). Save a PDF evidence pack with scanId/sha256 and Verify link for reproducible proof.