Re: [dmarc-ietf] DMARC alignment conflicts with RFC 5322 on the use of the From and Sender header fields

John Levine <johnl@taugh.com> Sun, 07 June 2020 21:40 UTC

Return-Path: <johnl@iecc.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 AB1F03A09C3 for <dmarc@ietfa.amsl.com>; Sun, 7 Jun 2020 14:40:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.851
X-Spam-Level:
X-Spam-Status: No, score=-1.851 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, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=guEl/WRg; dkim=pass (1536-bit key) header.d=taugh.com header.b=KZmFiLv1
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 UMmPdTNCr6UW for <dmarc@ietfa.amsl.com>; Sun, 7 Jun 2020 14:40:49 -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 373DE3A09C1 for <dmarc@ietf.org>; Sun, 7 Jun 2020 14:40:48 -0700 (PDT)
Received: (qmail 85054 invoked from network); 7 Jun 2020 21:40:46 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=14c3a.5edd5ede.k2006; bh=Dai7vKCR06Y87qrxk3lprmw6vZ3YH6v6IGBtojLQy5o=; b=guEl/WRgtYBvZa2i930+km1/wnwk5Ow1hiZMb9OaOgV3dkxqKWojZBQyzSwBwj6aPaiL0yoZcrM7VA9aLCZfOt2xaiVwOPhg6z5VQhPBnLBeC2K+IkMbcz8ZaQFXxgboG2wh9iZYYEAkajKHCirJCBbHdFKilsraVvUfG9r+GG8UbY4urLfYo1tQNPBZacK1EA8bKASrJgPURSoBGj3IfHSHpeWJVKGSCfZGlx7yJBDWGBnv3pS8Wiiax0rwGDEr
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=14c3a.5edd5ede.k2006; bh=Dai7vKCR06Y87qrxk3lprmw6vZ3YH6v6IGBtojLQy5o=; b=KZmFiLv1Q+WGfgZ31yQsZ1j9xNdhQdsGe5hzWGdkq4/7V8WiltAYZBkIhIE1/qjZFKuB52KTN0/XJDW7V7IDAmR3TrlnAIh94Z/7C9mEzv1O3EHW3VmE8vjJFz8c8hVQHtq0mck+EkyhC8xNB2k5eE+jk1i+G2SxO4vv7KerhNPH/xKvqu0w2lXx5Xu1j3/Ww2Bfm6I+L/Wb+ttLhoghGv/HRDDi0vM7xZvOKU0uzdOrejJ7MTOq/oWVHpiDoxyU
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTP via TCP6; 07 Jun 2020 21:40:45 -0000
Received: by ary.qy (Postfix, from userid 501) id E1CDB1A4634B; Sun, 7 Jun 2020 17:40:45 -0400 (EDT)
Date: Sun, 07 Jun 2020 17:40:45 -0400
Message-Id: <20200607214045.E1CDB1A4634B@ary.qy>
From: John Levine <johnl@taugh.com>
To: dmarc@ietf.org
Cc: stan@glyphein.mailforce.net
In-Reply-To: <71cddc80-008c-4f33-bdac-71ebc029bb3c@www.fastmail.com>
Organization: Taughannock Networks
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/wp3_VzZ2OZHhWxNSe4DfQUDqgEI>
Subject: Re: [dmarc-ietf] DMARC alignment conflicts with RFC 5322 on the use of the From and Sender header fields
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, 07 Jun 2020 21:40:51 -0000

In article <71cddc80-008c-4f33-bdac-71ebc029bb3c@www.fastmail.com> you write:
>I didn't know the history of the IETF's approach to UI, in particular, but I'm aware of the research on the nastiness of
>solving the UI problem.  I mostly wanted to clarify that the problem is, indeed, *how* to show that data to users, and that no
>one has actually ever been able to solve that problem.

I believe the real question is *whether* to show trust data to users
and the consensus seems to be don't bother, it only confuses them.

R's,
John