]> Taughannock Networks

PO Box 727 Trumansburg 14886 NY +1 831 480 2300 standards@taugh.com http://jl.ly

optivo GmbH

Wallstrasse 16 Berlin 10179 DE +49 30 768078 129 t.herkula@optivo.com https://www.optivo.com

Operations and Management email mailing list This document describes a method for signaling a one-click function for the list-unsubscribe email header. The need for this arises out of the actuality that mail software sometimes fetches URLs in mail headers, and thereby accidentally triggers unsubcriptions in the case of the list-unsubscribe header.

An email header can contain HTTP or HTTPS URIs. In a List-Unsubscribe Header the HTTP or HTTPS URI is intended to unsubscribe the recipient of the email from the list. But anti-spam software often fetches all resources in mail headers automatically, without any action by the user. As a result of this unintended malicious behavior, senders implement landing pages with a confirmation step to finish the unsubscribe request. If a mail recipient is unsubscribing manually, the confirmation page is presented to the recipient who can then click the appropriate button. But in some cases, there is no direct user interaction with the target web site, as when the unsubscription is a side effect of a spam report, or is performed automatically on mail sent to an abandoned mailbox. In those cases, the unsubscription process has to work without manual intervention, and in particular without requiring that software attempt to interpret the contents of a confirmation page. This document addresses this part of the problem, with a POST action for receivers that can be distinguished by senders from other requests and therefore handled as a one-click unsubscription without manual intervention by the mail recipient.

The capitalized key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in . One-click describes an action that directly triggers a change in a system's state, intended to be applied only with a user's intent.

This document has several goals. Allow email senders to signal "One-Click" functionality for specific HTTP and HTTPS URIs used in email headers. Allow MUA designers to implement independent user interface features for a better user experience. Allow MUA users to trigger intended actions in a familiar environment and without leaving the MUA context.

This document does not address problems associated with deliberate malicious behavior.

An entity which is responsible for sending an email that wishes to add an HTTP or HTTPS URI for one-click unsubscriptions places both a List-Unsubscribe and a List-Unsubscribe-Post header in the message. The List-Unsubscribe-Post header may contain multiple key value pairs needed by the sending entity. It also MUST contain the key value pair "List-Unsubscribe=One-Click". The combination of the URI in the List-Unsubscribe header and the POST arguments in the List-Unsubscribe-Post header MUST identify the mail recipient, so that the unsubscription process knows what address to handle. In particular, "one click" has no way to manually ask the user what address he or she wishes to unsubscribe. The sending entity needs to provide the infrastructure to handle POST requests to the specified URI in the List-Unsubscribe header. The "One-Click" action triggered by this URI SHOULD complete promptly and not burden the requester in an inappropriate way. The sending entity cannot expect that HTTP redirects are followed by the requester.

A receiving entity which wants to use a List-Unsubscribe HTTP URI from an email that also contains a List-Unsubscribe-Post header performs an HTTP or HTTPS POST to the first HTTP or HTTPS URI in the List-Unsubscribe header and send the content of the List-Unsubscribe-Post header as the request body. The POST content SHOULD be sent as "multipart/form-data" and MAY be sent as "application/x-www-form-urlencoded". These encodings are the ones used by web browsers when sending forms. The target of the POST action will typically be the same as or similar to the one in the manual confirmation page when doing a two-click unsubscribe, so this is intended to allow the same server code to handle both. The receiving entity MUST NOT perform a POST on the the HTTP or HTTPS URI without user consent. When and how the user consent is obtained is not part of this specification. The Request uses the HTTP or HTTPS verb POST. The HEAD and GET requests are not intended to be used to trigger a state change. PUT and DELETE would offer similar functionality but are often unavailable.

The email needs at least one valid authentication identifier. In this version of the specification the only supported identifier type is DKIM , that provides a domain-level identifier in the content of the "d=" tag of a validated DKIM-Signature header field. The List-Unsubscribe and List-Unsubscribe-Post headers need to be covered by the signature, and hence must be included in the "h=" tag of a valid DKIM-Signature header field.

IANA is requested to add a new entry to the Permanent Message Header Field Names registry. Header field name: List-Unsubscribe-Post Applicable protocol: mail Status: standard Author/Change controller: IETF Specification document: this document

Header in Email List-Unsubscribe-Post: List-Unsubscribe=One-Click&recip=user@example.com ]]>

Resulting POST request

Header in Email , List-Unsubscribe-Post: List-Unsubscribe=One-Click&recip=user@example.com ]]>

Resulting POST request

The List-Unsubscribe-Post header will typically contain the recipient address, but that address is usually also in the To: header. This specification allows anyone with access to a message to unsubscribe the recipient of the message, but that's typically the case with existing List-Unsubscribe, just with more steps. A creative mailer could send spam with content intended to provoke large numbers of unsubscriptions, with suitably crafted headers to send POST requests with arbitrary contents to servers that perhaps don't want them. But it's been possible to provoke GET requests in a similar way for a long time (and much easier, due to spam filter auto-fetches) so the chances of significantly increased annoyance seem low.

&RFC2119; &RFC2369; &RFC6376; &RFC7578;

Remove this section before publication, please.

Describe motivation in intro. Clarify required DKIM. More paranoid scenarios.