Re: [dmarc-ietf] Call for Adoption: DMARC Use of the RFC5322.Sender Header Field

John R Levine <johnl@taugh.com> Sun, 16 August 2020 18:16 UTC

Return-Path: <johnl@taugh.com>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC1E73A0FCA for <dmarc@ietfa.amsl.com>; Sun, 16 Aug 2020 11:16:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 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_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=iecc.com header.b=iKI3bDCR; dkim=pass (2048-bit key) header.d=taugh.com header.b=GXPmuJ3x
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 KA4KU2VHxkob for <dmarc@ietfa.amsl.com>; Sun, 16 Aug 2020 11:16:53 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 046173A0FC9 for <dmarc@ietf.org>; Sun, 16 Aug 2020 11:16:52 -0700 (PDT)
Received: (qmail 79216 invoked from network); 16 Aug 2020 18:16:51 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type; s=1356c.5f397813.k2008; i=johnl-iecc.com@submit.iecc.com; bh=giY4ayaa2qYPYj7sejE6IGBSNmtlXt5CgPUxWxn/xAg=; b=iKI3bDCRudiGgfJu55WTTLK5n3ZqwGLV3cKbPVN1Y+P6CnH2h05TP/x5CrKVORb46j34zdg/gYBaB/xGrs+ILIKfTDEt8zcLYvg4we+S9ikTflhhmnKI65A1e5cwHdrweWgoyrVFpryRtZVImMVdNMT/XSY1iC+yYQsLgEFI5ZHn6H/nehMabwNHiWMNsNc3RbGcL8nDtKyuXCMKuuoimlHGCdnOdGrTePET/4g2cIGKDFb4la2k7D4JRWO9/SCKw6y6D0Loo4ANbNB25CTw5bA7rBm8zf3HYU2UlwzyeyEYEJ0pOVGA+zlcCPAkcQKSHf7t6TEI5sOybJYdQNHmKA==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type; s=1356c.5f397813.k2008; olt=johnl-iecc.com@submit.iecc.com; bh=giY4ayaa2qYPYj7sejE6IGBSNmtlXt5CgPUxWxn/xAg=; b=GXPmuJ3xCVvykVmUX4BGW2DWu1jrRHI+RqiaUfViFQnV3ygguc9zj2kjyVPRGx1cLTRg8nz7q1YozxI7NqjO8rFwyjue73vcGmuL3BNZ8FInarKbMIAlOhp3hjJ1hqgtZBDi5zWVOw675wA1fFvamjHhuCaJ5idpWsHhl8ti9NfJZw/iRc5ErK0mwQ8yXLYirHQaNQZFNPQv5mBPew2eB52c8BKHrhQkxzeUX0dqoUnu84v6BYCrWrKEU3GPk4kb1tg2lqy6z6Y8+BGC9oUFq6E4O8M/wLvPhOEvqv0GbLDzT+7F0NodpEuDVqDlsGaw64Whmo8s4SiyqaqkjzlV7A==
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPSA (TLS1.3 ECDHE-RSA AES-256-GCM AEAD, johnl@iecc.com) via TCP6; 16 Aug 2020 18:16:50 -0000
Date: Sun, 16 Aug 2020 14:16:50 -0400
Message-ID: <b5935bde-e8-78ef-ed17-90a1d730aa9d@taugh.com>
From: John R Levine <johnl@taugh.com>
To: Alessandro Vesely <vesely@tana.it>
Cc: IETF DMARC WG <dmarc@ietf.org>
In-Reply-To: <13a0ed72-2c5a-8ba6-84ab-b857e29403f1@tana.it>
References: <CAJ4XoYcFbh8-nAxjxzzRgUahFfhcgcZQ2yMF2ewv_-DgUmhL=g@mail.gmail.com> <20200814164237.313071E971DB@ary.local> <CAJ4XoYeqj_5mpZu1PZP4rNfrWRyC5gC-2dfK7oX9xQHiR24QeA@mail.gmail.com> <085c6a5f-5451-ae8c-4873-133673ba1754@tana.it> <CAL0qLwaVUi9QtV4zcCwncuy4N3YPwsGZPzFfd1q19io79UG2VQ@mail.gmail.com> <c1844590-4b12-9763-21c5-6ac5b730321b@tana.it> <6358f3da-806b-f4eb-b9a0-8ee8ce4121d7@dcrocker.net> <4e549ca6-6047-6ff2-325c-fe8d7247e157@tana.it> <c972e0af-b589-1780-47b3-8cb2a2024ec2@dcrocker.net> <13a0ed72-2c5a-8ba6-84ab-b857e29403f1@tana.it>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="0-940272435-1597601810=:84766"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/W5x-J9U6oJEFKfu0k5-dUZ3nQjc>
Subject: Re: [dmarc-ietf] Call for Adoption: DMARC Use of the RFC5322.Sender Header Field
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmarc>, <mailto:dmarc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Aug 2020 18:16:55 -0000

On Sun, 16 Aug 2020, Alessandro Vesely wrote:
>>>> If I put my gmail address into the from field, there is no pretending, no 
>>>> matter what platform I am using.
>>> 
>>> That conflicts with the coarse-grained authentication strategy, 
>>> established at the FTC Email Authentication Summit in November
>>> 2004, as Doug^W Michael recalled. >
>> 1. I was making a semantic point, not a technical or technical policy one.
>
> They have to match at some point.

Sorry, that's just wrong.  There's no technical reason a mail message 
can't have any identifiers the sender wants.

>> 2. There was nothing 'established' at that event.  There were interesting 
>> discussions, but that's all.
>
> I wasn't there.  Can't it be considered the historic event that marked 
> domain-level authentication as the promising strategy to counter email abuse?

No, it was just some political theatre.  We were already working on SPF 
and DKIM.

> DMARC took that strategy to the extremes.  A number of users and operators 
> seem to have accepted it.  Why cannot we accept it too?

Please review the previous bazillion messages on this topic.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly