IETF Logo Mail Archive

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

Dave Crocker <dcrocker@gmail.com> Sun, 07 June 2020 23:17 UTC

Return-Path: <dcrocker@gmail.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 C278A3A079D for <dmarc@ietfa.amsl.com>; Sun, 7 Jun 2020 16:17:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, FREEMAIL_FROM=0.001, 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=gmail.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 QzU8p36nmh0Q for <dmarc@ietfa.amsl.com>; Sun, 7 Jun 2020 16:17:18 -0700 (PDT)
Received: from mail-ot1-x343.google.com (mail-ot1-x343.google.com [IPv6:2607:f8b0:4864:20::343]) (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 073403A07C5 for <dmarc@ietf.org>; Sun, 7 Jun 2020 16:17:17 -0700 (PDT)
Received: by mail-ot1-x343.google.com with SMTP id 97so810758otg.3 for <dmarc@ietf.org>; Sun, 07 Jun 2020 16:17:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=2d57HJzbniH4V6FA9e1bUiv3hgdo8ps+DtXcs6VjngU=; b=RkMSjGMIezyaaUbe6ZlfnFzzqE6tngR0dQOheX5X5VkhQUVOurmrGaRoDmUPNoJpa2 hlPaLel1gTY4bdIcuHbSOETGyrK0g9tXnsIrCzHoKS/B/9n3QqNFme1LY/Cwuo2Z4PLJ PKEofBGzAvueMsXuqNa2XtvMFxNXUiKR2CZHxAsbs42utQ8P02iDRo/xuu7EtqRRyB2L ftSwCajpm+uZm2yBNoZsVKepkVBenipiiu4IEr8ktFzHdpRxjHbXacec4CAKOnBDRRbi 5Q7q4v6FikdJ21VSQdHlvxMhulQ7+RZ4QrsL8hecaGeMAnakZ/YDGVe7e9P9FlCrx8eD uMvQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=2d57HJzbniH4V6FA9e1bUiv3hgdo8ps+DtXcs6VjngU=; b=gLeGC0d7qCQySLAPCcW//Kq85BRjoPIebVaAkx1DzSgvnJEfZV48L+LNXRtoLbWDWQ 0XqZ8wp8LHJ1lpSufWTcPBIt4Obz9jAazCIwW4npSGuDvZq47e6tkDCXtgu9ZWRKbhwd MkVOE5DqWpVLPxh4woDpEK+jcsTJNs5EtSGcm8ux7OieDei7oGD7nGD8U+eG9cgi4Mzu Hx05UG1rbULm5HkTmFxEbNXWX1kgC0gvVkyU0c/I/I0zHXPmQuwgyZY0XC8pqe33EVvd SqMoRcDvLp+xyg46nNaAlVZxEC3jsqjAAP7xX+fOLEdmybwDhaSu4NbTKVgDSYLZ92Rv 5DOA==
X-Gm-Message-State: AOAM531mRkmRPIjCd260w8/lwDrNSdkek5yQsspm42OgLoGoQdKrdmzM uucrnqrC+8yC/8WS03PCqEZ5jXnq
X-Google-Smtp-Source: ABdhPJyeLNuQZJd4zajQLJx2KJoZ0AUhC4xG8ff52OUO34zsz2jK/zBitsrH1K3ftmvJ0KCmRYJPjA==
X-Received: by 2002:a9d:7083:: with SMTP id l3mr10300436otj.232.1591571837387; Sun, 07 Jun 2020 16:17:17 -0700 (PDT)
Received: from ?IPv6:2600:1700:a3a0:4c80:5443:4b56:d117:6ef3? ([2600:1700:a3a0:4c80:5443:4b56:d117:6ef3]) by smtp.gmail.com with ESMTPSA id w132sm2054563oib.30.2020.06.07.16.17.16 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 07 Jun 2020 16:17:16 -0700 (PDT)
To: John Levine <johnl@taugh.com>, dmarc@ietf.org
Cc: stan@glyphein.mailforce.net
References: <20200607214045.E1CDB1A4634B@ary.qy>
From: Dave Crocker <dcrocker@gmail.com>
Message-ID: <06db657a-2b87-2bb0-6e80-f58de8fc9930@gmail.com>
Date: Sun, 07 Jun 2020 16:17:15 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.9.0
MIME-Version: 1.0
In-Reply-To: <20200607214045.E1CDB1A4634B@ary.qy>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/qA0A5Mnlblsd8LwRU0WVSYypxUY>
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 23:17:26 -0000

On 6/7/2020 2:40 PM, John Levine wrote:
> 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.


It's not that it 'seems to be'. It isn't nearly that soft.

It is that there have been multiple efforts over the years and none has 
demonstrated efficacy.

Anyone claiming the contrary needs to provide objective data to 
substantiate a claim of efficacy.

Adding a capability or relying one carries an affirmative obligation to 
provide a basis for knowing that the cost is justified. So far, there 
isn't one, for end-user trust notifications.


d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

v2.23.0 | Report a Bug | By Email