[dispatch] Discussion about draft-benecke-cfbl-address-header

Jan-Philipp Benecke <jpb@cleverreach.com> Fri, 14 January 2022 19:24 UTC

Return-Path: <jpb@cleverreach.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E42B03A0CB0 for <dispatch@ietfa.amsl.com>; Fri, 14 Jan 2022 11:24:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=cleverreach.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GILxNRJAsP0X for <dispatch@ietfa.amsl.com>; Fri, 14 Jan 2022 11:23:58 -0800 (PST)
Received: from mail-lf1-x132.google.com (mail-lf1-x132.google.com [IPv6:2a00:1450:4864:20::132]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 15DAF3A0CA3 for <dispatch@ietf.org>; Fri, 14 Jan 2022 11:23:58 -0800 (PST)
Received: by mail-lf1-x132.google.com with SMTP id bu18so10404151lfb.5 for <dispatch@ietf.org>; Fri, 14 Jan 2022 11:23:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cleverreach.com; s=gsuite; h=message-id:date:mime-version:user-agent:content-language:from :organization:subject:to:content-transfer-encoding; bh=Obt2ITb4wXiKFwWVuehyd3JG9BrCPMKB1G3k9DO4us4=; b=gXj42/Z+hbzQC0tF/nhjvrQG0ISPek1W8C7LhzbL7s8aylBchZl7PA/Q7gwB55D56Y ILT1+51pMpczluP3+CmY7+2CyA8cx+3TT/uq4bGPhJYkz3/SUV4OCsAJce5RbHtaYAXT Urq4fj+8mhECZuhUmwNPUM66izko/gIfL4I7ovxVx3AJZH1BXkiwg8RwEbGxJl9KyDUW CdzOl7cob31ccheLFikDv4B4PIwGitQ+QhzA7P7fK8tDdaO2+1zwkSVu04ItTP9lkN6b 7wWARmKg90Dsz3D9Y6CUSzQTCQHtnaa02DMjogHu+RsphMtnBrHnKwqypD9Q75JNk7qa QCMw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent :content-language:from:organization:subject:to :content-transfer-encoding; bh=Obt2ITb4wXiKFwWVuehyd3JG9BrCPMKB1G3k9DO4us4=; b=n0z0secPr5TCZTzfrF3Cz3NkIY6uesNiTpIoGjCoh0pd9oORztykqs4NdSZaeV/aQ7 YeXH+j6AvRq4U72blo7Dun0Af/uTnevxSd3TbmzakG1V3mOPjEki7X1PI0W1G16Rk/B8 P4+17mwHLpc5NQeXqkhZ5DIvGmoT01CWcIcRtj6Fw9fcAwBOfzeST41sMQwnciZBRhsa NewHN7cUgLR0+NTdXt2TqlV836LIOikjUIOFHyxEprShg1CiacfbEV/8RHpJRv6i7RBV 8M20Q72aGj6zrZKSQV+40bnUXvgZNAul03MkJofEoBY9zM3ShN5MFXYXVPb8OzSXMbUp nYKw==
X-Gm-Message-State: AOAM531sbjBK5o7y61kwaAdeKTuk8i9oZ91cR5L+Ox2b7DLmPap8WA46 F2bjcSapMDxR/gO4qmse3Ni4REiUlw4x7w==
X-Google-Smtp-Source: ABdhPJwIh2cw2PhuMYYBdRKELDi3BrJ6WHLKGRs3meaDgD74zAHndS5iugrF6YcyHO5LKTgCUjL3CQ==
X-Received: by 2002:a05:651c:996:: with SMTP id b22mr7214553ljq.496.1642188235034; Fri, 14 Jan 2022 11:23:55 -0800 (PST)
Received: from ?IPV6:2a01:c23:78c1:6200:156d:7a73:9bf7:1e73? (dynamic-2a01-0c23-78c1-6200-156d-7a73-9bf7-1e73.c23.pool.telefonica.de. [2a01:c23:78c1:6200:156d:7a73:9bf7:1e73]) by smtp.gmail.com with ESMTPSA id j12sm663529lfu.25.2022.01.14.11.23.54 for <dispatch@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 14 Jan 2022 11:23:54 -0800 (PST)
Message-ID: <4675435d-f889-b0a2-e74a-6e4b2f1d963c@cleverreach.com>
Date: Fri, 14 Jan 2022 20:23:53 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.4.1
Content-Language: en-US
From: Jan-Philipp Benecke <jpb@cleverreach.com>
Organization: CleverReach GmbH & Co.KG
To: dispatch@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/s2lB4VhJUlbDE46etf3PyKMr_Ro>
Subject: [dispatch] Discussion about draft-benecke-cfbl-address-header
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Jan 2022 19:31:41 -0000

Hey dispatch wg!

First of all, I would like to introduce myself briefly:
My name is Jan-Philipp Benecke, i work as a Deliverability & Software
Engineer at CleverReach GmbH & Co.KG.
We're a email marketing provider offering a software-as-a-service for
sending email campaigns and transactional mails.
This is my first IETF related work, so i'm a newbie when coming to this :)

I want to introduce you my email-related draft "Complaint Feedback Loop
Address Header" which can be found @
https://datatracker.ietf.org/doc/draft-benecke-cfbl-address-header/.
The intention of this draft is to have documented, standardized and
automated way to provide a so called complaint feedback loop address to
mailbox providers.
Currently, providing and maintaining such an address is a manual and
time-consuming process for both sides, email senders and mailbox providers.
This draft defines the required header, how the header needs to be
processed and signed by DKIM.

Now i want to kick off a discussion around the draft and collect
feedback. This draft has already been presented to the ISE, Adrian
advised me to introduce the draft to this wg for further review and
discussion.

There has been already a heavy discussion while writing within the
Certified Senders Alliance (https://certified-senders.eu/), which is an
association of mailbox providers and senders.
The conclusion of this discussion was that a larger majority is
interested in such an automated path.
For example, 1&1 Mail & Media, the company behind web.de/gmx.de/mail.com
(major mailbox provider in Germany), is very interested in this draft
and would be happy to have this.
The same feedback i already got from some email senders i'm in contact with.

I look forward to hear your feedback about this draft.

Best,
Jan-Philipp