CleverReach GmbH & Co. KG

Schafjueckenweg 2 Rastede 26180 Germany +49 4402 97390-16 jpb@cleverreach.com

art Network Working Group Internet-Draft This document describes a method to allow a mail sender to specify a complaint feedback loop address as an email header and how a mail receiver can use it. This document also defines the rules for processing and forwarding such a complaint. The motivation for this arises out of the absence of a standardized and automated way to provide a complaint feedback loop address to mailbox providers. Currently, providing and maintaining such an address to a mailbox provider is a manual and time-consuming process.

Since a long time there is a way to forward manual complaints back to e.g. a broadcast marketing list operator. The mailbox provider provides a so-called feedback loop . This feedback loop is being used to give e.g. operators of broadcast marketing lists feedback about resulting complaints from their marketing mailings. Those complaints are based on manual user interaction e.g. IMAP movement to "Junk". As described in the registration for such a feedback loop needs to be done manually by a human at any FBL provider he wants to receive complaints from. Which can be quite time-consuming if there are new feedback loops rising up, or the mail sender wants to add new ip addresses or DKIM domains. Besides, a manual process isn't well suitable and/or doable for smaller mailbox providers. The change of such a complaint address e.g. due to an infrastructure change is another problem. Due to this manual process the mail sender needs to go through all providers again and delete his existing subscriptions and re-signup with the new complaint address. This document addresses this problem with a new email header. It extends the described complaint feedback loop recommendations in with an automated way to provide the complaint feedback loop address to mail receiver. Mail senders can add this header and willing mailbox provider can use this header to forward the generated report to the provided complaint address. The mail sender just needs to add a email header and isn't required to signup manually at every feedback loop provider. Another benefit would be the mailbox provider doesn't need to develop a manual registration process and verification process. A new email header has been chosen over a new DNS record in favour to be able to easily distinguish between multiple broadcast marketing list operators / mail senders, without the intervention of its users or administrators. For example, if a company uses multiple sending systems, each system can set this header on their own, without the need of a change that has to be done by its users or administrators. On the side of the mailbox provider, there is no need to do an additional DNS query to get the complaint address. This document has been created with GDPR and other data-regulation laws in mind and to address the resulting problems in providing an automated complaint feedback loop address, as the email may contain personal data. Summarised this document has following goals: Allow mail senders to signal that there is a complaint address without a manual registration at all providers. Have a way for mailbox provider to get a complaint address without developing an own manual registration process. Be able to provide a complaint address to smaller mailbox providers who do not have a feedback loop registration process. Provide a GDPR compliant way for a complaint feedback loop

The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 when, and only when, they appear in all capitals, as shown here. The keyword "FBL" in this document is the abbreviation for "feedback loop" and will hereafter be used. The keyword "CFBL" in this document is the abbreviation for "complaint feedback loop" and will hereafter be used. The keyword "MBP" in this document is the abbreviation for "mailbox provider" and will hereafter be used.

The email (sent by mail sender/broadcast marketing list operator) about which a complaint should be sent MUST have at least one valid signature, which covers the From-Header domain. The email about which a complaint should be sent MUST be aligned as specified in . The Complaint-FBL-Address header MUST be covered by the signature, it MUST be included in the "h=" tag of the valid DKIM-Signature header field. If the message isn't properly aligned, nor it does have the required header coverage by , the MBP SHOULD NOT send a report email. This ensures that only reports are sent to the complaint address that are based on an authenticated email.

The report email (sent by MBP to mail sender) MUST have a valid signature and MUST cover the From-Header domain. If the message does not have the required valid , the mail sender SHOULD NOT process this email. It is highly RECOMMENDED that the mail sender does further plausibility checks.

A mail sender that wishes to receive complaints about their mailings MUST place a Complaint-FBL-Address in the message. The mail sender MAY place a Feedback-ID header in the message out of various reasons. The receiving complaint FBL address, placed in the message, MUST accept compatible reports. It is highly RECOMMENDED processing these ARF reports automatically and unsubscribe the complaining receivers. The mail sender MUST take action to address the described requirements in .

An MBP MAY process the complaint and forward it to the complaint FBL address. If the MBP wants to process the complaints and forwards it, he MUST query the Complaint-FBL-Address header. An compatible report MUST be sent when a manual action has been taken, e.g. when a receiver marks a mail as spam, by clicking the "This is spam"-button in any web portal or by moving a mail to junk folder, this includes also IMAP/POP3 movements. The MBP SHOULD NOT send any report when an automatic decisions has been made, e.g. spam filtering. The MBP MUST validate and take action to address the described requirements in .

The complaint report (sent by MBP to mail sender) MUST be an report. The report MUST contain at least the Message-ID or the header "Feedback-ID" of the complaining email. The MBP MAY omit all further headers and/or body to comply with any data-regulation laws. It is highly RECOMMENDED that, if used, the Feedback-ID includes a hard to forge component such as an using a secret key, instead of a plain-text string.

The following ABNF imports fields, WSP, CRLF and addr-spec from .

" CRLF ]]>

The following ABNF imports fields, WSP, CRLF and atext from . It imports ALPHA and DIGIT from .

This section discusses possible security issues, and their possible solutions, of a complaint FBL address header.

As any other email address, a complaint FBL addresses can be an attack vector for malicious emails. The complaint FBL addresses can be for example flooded with spam. This is an existing problem with any existing email address and isn't newly created by this document. The broadcast marketing lists operator/mail sender must take appropriated measures. One possible countermeasure would be a rate limit on the delivering IP. However, this should be done with caution, the normal FBL email traffic must not be impaired.

A malicious person can send a bunch of forged ARF reports to a known complaint FBL addresses and try to guess a Message-ID/Feedback-ID. He might try to do a mass-unsubscription of a complete marketing list. This is also an already existing problem with the current FBL implementation. The receiving broadcast marketing lists operator/mail sender must take appropriated measures. As a countermeasure it is recommended that the Message-ID and, if used, Feedback-ID uses a hard to forge component such as an using a secret key, instead of a plain-text string, to make an enumeration attack impossible. If it is impossible for the broadcast marketing lists operator/mail sender to use a hard to forge component, the broadcast marketing lists operator/mail sender should take measures to avoid enumeration attacks.

Providing such a header itself doesn't produce a data-regulation law problem. The resulting ARF report, that is sent to the mail sender by the MBP, may conflict with a data-regulation law, as it may contain personal data. This document already addresses some parts of this problem and describes a data-regulation law safe way to send a FBL report. As described in , the MBP may omit the complete body and/or headers and just sends the required fields. Nevertheless, each MBP must consider on their own, if this implementation is acceptable and complies with the existing data-regulation laws. As described in , it is also highly RECOMMENDED that the Message-ID and, if used, the Feedback-ID includes a hard to forge component such as an using a secret key, instead of a plain-text string. See for an example. Using HMAC, or any other hard to forge component, ensures that only the mail sender has knowledge about the data.

The IANA is requested to register a new header field, per , into the "Permanent Message Header Field Names" registry:

Specification document: this document ]]>

The IANA is requested to register a new header field, per , into the "Permanent Message Header Field Names" registry:

Specification document: this document ]]>

For simplicity the DKIM header has been shortened.

Email about the report will be generated:

From: Awesome Newsletter To: me@example.net Subject: Super awesome deals for you Complaint-FBL-Address: Message-ID: Content-Type: text/plain; charset=utf-8 This is a super awesome newsletter. ]]>

Resulting ARF report:

From: Awesome Newsletter To: me@example.net Subject: Super awesome deals for you Complaint-FBL-Address: Message-ID: Content-Type: text/plain; charset=utf-8 This is a super awesome newsletter. ------=_Part_240060962_1083385345.1592993161900-- ]]>

Email about the report will be generated:

From: Awesome Newsletter To: me@example.net Subject: Super awesome deals for you Complaint-FBL-Address: Message-ID: Feedback-ID: 111:222:333:4444 Content-Type: text/plain; charset=utf-8 This is a super awesome newsletter. ]]>

Resulting ARF report contains only the Feedback-ID:

Email about the report will be generated:

From: Awesome Newsletter To: me@example.net Subject: Super awesome deals for you Complaint-FBL-Address: Message-ID: Feedback-ID: 3789e1ae1938aa2f0dfdfa48b20d8f8bc6c21ac34fc5023d63f9e64a 43dfedc0 Content-Type: text/plain; charset=utf-8 This is a super awesome newsletter. ]]>

Resulting ARF report contains only the Feedback-ID:

Technical and editorial reviews and comments were provided by colleagues at CleverReach, and the colleagues at Certified Senders Alliance. Legal reviews and comments were provided by the colleagues at the Certified Senders Alliance.

In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings. DomainKeys Identified Mail (DKIM) permits a person, role, or organization that owns the signing domain to claim some responsibility for a message by associating the domain with the message. This can be an author's organization, an operational relay, or one of their agents. DKIM separates the question of the identity of the Signer of the message from the purported author of the message. Assertion of responsibility is validated through a cryptographic signature and by querying the Signer's domain directly to retrieve the appropriate public key. Message transit from author to recipient is through relays that typically make no substantive change to the message content and thus preserve the DKIM signature.This memo obsoletes RFC 4871 and RFC 5672. [STANDARDS-TRACK] This document specifies the Internet Message Format (IMF), a syntax for text messages that are sent between computer users, within the framework of "electronic mail" messages. This specification is a revision of Request For Comments (RFC) 2822, which itself superseded Request For Comments (RFC) 822, "Standard for the Format of ARPA Internet Text Messages", updating it to reflect current practice and incorporating incremental changes that were specified in other RFCs. [STANDARDS-TRACK] Domain-based Message Authentication, Reporting, and Conformance (DMARC) is a scalable mechanism by which a mail-originating organization can express domain-level policies and preferences for message validation, disposition, and reporting, that a mail-receiving organization can use to improve mail handling.Originators of Internet Mail need to be able to associate reliable and authenticated domain identifiers with messages, communicate policies about messages that use those identifiers, and report about mail using those identifiers. These abilities have several benefits: Receivers can provide feedback to Domain Owners about the use of their domains; this feedback can provide valuable insight about the management of internal operations and the presence of external domain name abuse.DMARC does not produce or encourage elevated delivery privilege of authenticated email. DMARC is a mechanism for policy distribution that enables increasingly strict handling of messages that fail authentication checks, ranging from no action, through altered delivery, up to message rejection. This document defines an extensible format and MIME type that may be used by mail operators to report feedback about received email to other parties. This format is intended as a machine-readable replacement for various existing report formats currently used in Internet email. [STANDARDS-TRACK] Internet technical specifications often need to define a formal syntax. Over the years, a modified version of Backus-Naur Form (BNF), called Augmented BNF (ABNF), has been popular among many Internet specifications. The current specification documents ABNF. It balances compactness and simplicity with reasonable representational power. The differences between standard BNF and ABNF involve naming rules, repetition, alternatives, order-independence, and value ranges. This specification also supplies additional rule definitions and encoding for a core lexical analyzer of the type common to several Internet specifications. [STANDARDS-TRACK] Complaint Feedback Loops similar to those described herein have existed for more than a decade, resulting in many de facto standards and best practices. This document is an attempt to codify, and thus clarify, the ways that both providers and consumers of these feedback mechanisms intend to use the feedback, describing some already common industry practices.This document is the result of cooperative efforts within the Messaging Anti-Abuse Working Group, a trade organization separate from the IETF. The original MAAWG document upon which this document is based was published in April, 2010. This document does not represent the consensus of the IETF; rather it is being published as an Informational RFC to make it widely available to the Internet community and simplify reference to this material from IETF work. This document is not an Internet Standards Track specification; it is published for informational purposes. This document describes HMAC, a mechanism for message authentication using cryptographic hash functions. HMAC can be used with any iterative cryptographic hash function, e.g., MD5, SHA-1, in combination with a secret shared key. The cryptographic strength of HMAC depends on the properties of the underlying hash function. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind This specification defines registration procedures for the message header fields used by Internet mail, HTTP, Netnews and other applications. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.