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

Dave Crocker <dhc@dcrocker.net> Tue, 29 September 2020 00:54 UTC

Return-Path: <dhc@dcrocker.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 A494D3A0766 for <dmarc@ietfa.amsl.com>; Mon, 28 Sep 2020 17:54:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.112
X-Spam-Level:
X-Spam-Status: No, score=-2.112 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.213, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 Nl2FeeuSC3dN for <dmarc@ietfa.amsl.com>; Mon, 28 Sep 2020 17:54:12 -0700 (PDT)
Received: from simon.songbird.com (simon.songbird.com [72.52.113.5]) (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 159D03A05AC for <dmarc@ietf.org>; Mon, 28 Sep 2020 17:54:12 -0700 (PDT)
Received: from [192.168.0.109] (c-24-130-62-181.hsd1.ca.comcast.net [24.130.62.181]) (authenticated bits=0) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1.1) with ESMTP id 08T0vJa8014664 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Mon, 28 Sep 2020 17:57:19 -0700
To: Scott Kitterman <sklist@kitterman.com>
References: <20200927171611.838B321D9BAD@ary.qy> <5069099.lO0Lvmlme3@zini-1880> <CABuGu1oSshRN20twB6w1r6bnDDt8sunkPG9JY=V8Nme1Y5hVUg@mail.gmail.com> <33363154.Bvymkppg8h@zini-1880>
Cc: dmarc@ietf.org
Reply-To: dcrocker@bbiw.net
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <de05659a-91ed-0c76-3d8d-766d85475585@dcrocker.net>
Date: Mon, 28 Sep 2020 17:54:05 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.12.0
MIME-Version: 1.0
In-Reply-To: <33363154.Bvymkppg8h@zini-1880>
Content-Type: multipart/alternative; boundary="------------B5C7434BE6C6659780216158"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/nFwlZOAljjO3dq-MWjXQrn1fvfM>
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: Tue, 29 Sep 2020 00:54:14 -0000

On 9/28/2020 5:32 PM, Scott Kitterman wrote:
> but
> pretending like DMARC policy doesn't exist is not.

Claims of pretending seem to be popular just now.  the problem seems to 
be adequately explaing  the pretending.

So to contribute the response portion of this ritual:

    1. No one is pretending anything.

    2. Since you believe otherwise, please document it.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net