Re: [dmarc-ietf] Sender vs From Addresses

Charles Gregory <Charles@possumdelight.com> Wed, 24 March 2021 18:17 UTC

Return-Path: <Charles@possumdelight.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 97BB33A32C5 for <dmarc@ietfa.amsl.com>; Wed, 24 Mar 2021 11:17:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, 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 ApA8p6b3SOPO for <dmarc@ietfa.amsl.com>; Wed, 24 Mar 2021 11:17:32 -0700 (PDT)
Received: from mail.possumdelight.com (mail.possumdelight.com [107.130.215.19]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0B2E63A32B5 for <dmarc@ietf.org>; Wed, 24 Mar 2021 11:17:31 -0700 (PDT)
Received: from EX.possumdelight.com (fd07::1:0:0:1:4) by EX.possumdelight.com (fd07::1:0:0:1:4) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.2.792.3; Wed, 24 Mar 2021 14:17:30 -0400
Received: from EX.possumdelight.com ([fe80::ad5d:d7f1:b37d:a89f]) by EX.possumdelight.com ([fe80::ad5d:d7f1:b37d:a89f%7]) with mapi id 15.02.0792.010; Wed, 24 Mar 2021 14:17:30 -0400
From: Charles Gregory <Charles@possumdelight.com>
To: Dave Crocker <dcrocker@gmail.com>, Ken O'Driscoll <ken=40wemonitoremail.com@dmarc.ietf.org>
CC: IETF DMARC WG <dmarc@ietf.org>
Thread-Topic: [dmarc-ietf] Sender vs From Addresses
Thread-Index: AdcgkuKhihmmxnZnSJC0xMH2ibjOrQADKZuQABU22QD//8sfnw==
Date: Wed, 24 Mar 2021 18:17:30 +0000
Message-ID: <ed880cdedca24494ab474fbf1578bac9@possumdelight.com>
References: <6cacad89cb2049858938fce107d60dd9@possumdelight.com> <VI1PR01MB7053E1ED6ED09791428D6EE4C7639@VI1PR01MB7053.eurprd01.prod.exchangelabs.com>, <03a570ad-c66a-c7b7-29d6-28ba6edab459@gmail.com>
In-Reply-To: <03a570ad-c66a-c7b7-29d6-28ba6edab459@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: multipart/alternative; boundary="_000_ed880cdedca24494ab474fbf1578bac9possumdelightcom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/f09iGimMsdDHiHZbsKfidt4XwyE>
Subject: Re: [dmarc-ietf] Sender vs From Addresses
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: Wed, 24 Mar 2021 18:17:41 -0000

Thank you for the replies gentlemen.  This draft exactly what we are needing!

Responsible users want to be able to send to e-mail lists as themselves and have replies go to themselves while bounces go to a central system inbox (info@mailprocessingdomain.com) return-path address for processing and database cleanup - without risk of lower deliverability rates.

Honestly, I can't believe this wasn't considered.

I realize changes like this take a long time to roll out / be adopted; but what's involved in getting this "unstuck?  Honestly I have no idea how these things happen.

Charles Gregory


Sent from my T-Mobile 4G LTE Device



-------- Original message --------
From: Dave Crocker <dcrocker@gmail.com>
Date: 3/24/21 1:27 PM (GMT-05:00)
To: Ken O'Driscoll <ken=40wemonitoremail.com@dmarc.ietf.org>, Charles Gregory <Charles@possumdelight.com>
Cc: IETF DMARC WG <dmarc@ietf.org>
Subject: Re: [dmarc-ietf] Sender vs From Addresses

On 3/24/2021 4:54 AM, Ken O'Driscoll wrote:
There is actually an existing working group draft discussing extending DMARC to incorporate the 5322.Sender header, see https://datatracker.ietf.org/doc/draft-ietf-dmarc-sender/. That document goes into considerable detail on how 5322.Sender could be incorporated in the future.


To be possibly overly frank, I think the draft is stalled.  Given existing practice, there are challenges to fielding this, for incremental adoption, in a way that is reasonable and useful.  (The Internet does not support 'flag' days.)

I am still, sometimes, mulling over the choices for this, but so far haven't come up with (or seen) ways to resolve the challenge.

An option the working group declined to pursue is to define an Author: field and leave the From: field to the 'handling' role DMARC has relegated it to.  The draft for this is being pursued outside of the working group.


d/

--
Dave Crocker
dcrocker@gmail.com<mailto:dcrocker@gmail.com>
408.329.0791

Volunteer, Silicon Valley Chapter
Information & PLanning Coordinator
American Red Cross
dave.crocker2@redcross.org<mailto:dave.crocker2@redcross.org>