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

Stan Kalisch <stan@glyphein.mailforce.net> Sun, 07 June 2020 20:23 UTC

Return-Path: <stan@glyphein.mailforce.net>
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 9C85A3A0907 for <dmarc@ietfa.amsl.com>; Sun, 7 Jun 2020 13:23:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=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=mailforce.net header.b=sc1o3157; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=HM9AAwUI
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 oT6EJQgt5oaT for <dmarc@ietfa.amsl.com>; Sun, 7 Jun 2020 13:23:47 -0700 (PDT)
Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 679073A0902 for <dmarc@ietf.org>; Sun, 7 Jun 2020 13:23:47 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.west.internal (Postfix) with ESMTP id BA228404 for <dmarc@ietf.org>; Sun, 7 Jun 2020 16:23:46 -0400 (EDT)
Received: from imap6 ([10.202.2.56]) by compute2.internal (MEProxy); Sun, 07 Jun 2020 16:23:46 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mailforce.net; h=mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type; s=fm3; bh=ZKalgwBjrgOp3j3ksDU0DxW1BGfoNHF PP+AP7qZIe+k=; b=sc1o31570AE6vb0H/46JwTGrAumOr5lmhkjKB5Z9/8sugQt Ig1LN8PTKdefwfv2/gg5RdEbLZ4JxBK7vVmScyQ798HbLEO80XSUN0xJt6bVlQgX X8lDSqJeSfJseRDdaRYW+OGsbgtxgjgIst1S4x4y+PnKPvC/RUr2KipQBQT9IGUa MMmFFM/tTMgObVmpcMf7+BbMGEKVb5/ugjYPYHzU5R7Qm3c0sqejGTrJuEDkYqB9 EcduOsG/kvWG2pbAiJOXDI+69SUKy1exeNNyOp1RB3/w/2i4C7sA/2MWk2Z7IZoi bjxSHx4xMpH5CuTimv4WJAGO3lhMMlHX4s10FkQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=ZKalgw BjrgOp3j3ksDU0DxW1BGfoNHFPP+AP7qZIe+k=; b=HM9AAwUIXisEREIxOWhROM lnHteq6feU4h/0FvDB42VtjuCT1Yzk4ZGsT82C1sVdV2u7r4PTi5moirhhCxKtZI lFvtl5RCNZyVnRz1AwFctfoR1hh7HGp65Z5b3QVujSo7lfu6X0Ft9NjUGQFz7Fom xjEEakycPyB8p/8Rb6fvdatI6EunasBe031FIcVEKXkwyE41DISaUvDSXxj+/AqE WzafFQPSmL2ajsFYamTe/h2W2D7Map1Od8Zc1kms+NVnS9zc5m9Yv77xoKgujKCA DBH4Sg+xv60MBZldJn0nCV1n/NcromDEzuSO5GScaPbUOYDQJW+CNg9C2O4yDpEQ ==
X-ME-Sender: <xms:0kzdXmLMLX5W3Sm0vhcWovg0eYN2p7vYab85FIqaW0B-unrwP4pfmw>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedrudegledgudehvdcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesth dtredtreerjeenucfhrhhomhepfdfuthgrnhcumfgrlhhishgthhdfuceoshhtrghnsehg lhihphhhvghinhdrmhgrihhlfhhorhgtvgdrnhgvtheqnecuggftrfgrthhtvghrnhepff dufedutdegvdefvdeihfeiueffgeekkeeftefghfelheevhfefleeileehfeeknecuffho mhgrihhnpehfrghsthhmrghilhdrtghomhenucevlhhushhtvghrufhiiigvpedtnecurf grrhgrmhepmhgrihhlfhhrohhmpehsthgrnhesghhlhihphhgvihhnrdhmrghilhhfohhr tggvrdhnvght
X-ME-Proxy: <xmx:0kzdXuItbo2Qb9G2kaHF6DzzdyRRPfnoLtoF8e9D9jNDugXvQAzDLw> <xmx:0kzdXmvt2nSpQpVo-qfyg_JwOV7mDLkkedcnk_72c2cWY0YZ2CqZbA> <xmx:0kzdXrakDGADSfHNVUgfnk-88xdwpucCq75ygBJBiMiMjgHmVEsHuQ> <xmx:0kzdXtokawYYfu6NZFgXGbSFBDnPnE5ZGuDr-81DaOjHy3HmDgzvqw>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 17C261400A1; Sun, 7 Jun 2020 16:23:46 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.3.0-dev0-519-g0f677ba-fm-20200601.001-g0f677ba6
Mime-Version: 1.0
Message-Id: <71cddc80-008c-4f33-bdac-71ebc029bb3c@www.fastmail.com>
In-Reply-To: <20200607195228.70FC51A44FEC@ary.qy>
References: <20200607195228.70FC51A44FEC@ary.qy>
Date: Sun, 07 Jun 2020 16:23:24 -0400
From: Stan Kalisch <stan@glyphein.mailforce.net>
To: dmarc@ietf.org
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/oFy8_qCIWysgC-fOpOgum1NcvNI>
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 20:23:49 -0000

On Sun, Jun 7, 2020, at 3:52 PM, John Levine wrote:
> In article <46e045ae-9691-4f5b-86bf-142c066458d8@www.fastmail.com> you write:
> >-=-=-=-=-=-
> >
> >On Sun, Jun 7, 2020, at 9:16 AM, Douglas E. Foster wrote:
> >> 3) Some of the discussion has been about how to prevent soclal engineering of the recipient user. This is an important
> >topic, but not directly related to the project. IETF would do well to establish some recommendations about how MUAs should
> >behave, so that trust data can be displayed to the user.
> >
> >Assuming this can be practically done, I would rephrase this, "...[E]stablish how MUAs should display trust data to users."
> 
> We have decades of experience that tells us that the IETF is hopeless
> at UI design, and our intuition is usually wrong.
> 
> In particular, displaying warnings that "this may be bad" or even
> "this is extremely bad" is known not to work. No matter what you say,
> people will click through any warning to get to their kitten GIFs or
> porn or whatever.

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.


Thanks,
Stan