Re: [dmarc-ietf] Sender vs From Addresses

Hector Santos <hsantos@isdg.net> Thu, 25 March 2021 22:26 UTC

Return-Path: <hsantos@isdg.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 84F4D3A0C86 for <dmarc@ietfa.amsl.com>; Thu, 25 Mar 2021 15:26:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level:
X-Spam-Status: No, score=-2.101 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, NICE_REPLY_A=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isdg.net header.b=TzJe2oUQ; dkim=pass (1024-bit key) header.d=beta.winserver.com header.b=Yfy5QinK
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 rLOCsdzbff4d for <dmarc@ietfa.amsl.com>; Thu, 25 Mar 2021 15:26:10 -0700 (PDT)
Received: from mail.winserver.com (winserver.com [76.245.57.69]) (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 D64FB3A0C84 for <dmarc@ietf.org>; Thu, 25 Mar 2021 15:26:09 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha256; c=simple/relaxed; l=2020; t=1616711166; atps=ietf.org; atpsh=sha1; h=Received:Received:Received:Received:Message-ID:Date:From: Organization:To:Subject:List-ID; bh=1dRPlac1uXXGO3FfsR0K3UeRd2nv pV9KhJruEDEtVbE=; b=TzJe2oUQRkqxyqdOoUsgk08MyiId4/OrSa7MLNFxgQcD En6WejxyyqU2qdSBmZREw+Kuu06fn9CQ9NIzI3o23EWrt6D4tukJ7C36gY3PUqgp Vh5gmrMvMnZ3LHDijZIOsf6K7NL3ff5olAoUAKlPDx4QxRub/OCdlvzVyCqoVHM=
Received: by mail.winserver.com (Wildcat! SMTP Router v8.0.454.10) for dmarc@ietf.org; Thu, 25 Mar 2021 17:26:05 -0500
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com; dmarc=pass policy=reject author.d=isdg.net signer.d=beta.winserver.com (atps signer);
Received: from beta.winserver.com ([76.245.57.74]) by mail.winserver.com (Wildcat! SMTP v8.0.454.10) with ESMTP id 744355168.19922.3544; Thu, 25 Mar 2021 17:26:05 -0500
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=2020; t=1616711169; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=1dRPlac 1uXXGO3FfsR0K3UeRd2nvpV9KhJruEDEtVbE=; b=Yfy5QinK/k0Vh8lWyN9HnuN CCYuKVlA6mE7Lk7Q+mfYFNCIonjWXCF0R8cpWdPaX91+1VZNdUoUAIMZ6tWPue23 PTrOeTpa2eYR+PUpf37CsioeqkZpqpSk8+JYEOQFQiVJOpneQFBF19z0ROsAye26 q4O/rO39vzOAbP0J3aFE=
Received: by beta.winserver.com (Wildcat! SMTP Router v8.0.454.10) for dmarc@ietf.org; Thu, 25 Mar 2021 18:26:08 -0400
Received: from [192.168.1.68] ([75.26.216.248]) by beta.winserver.com (Wildcat! SMTP v8.0.454.10) with ESMTP id 1428013362.1.23164; Thu, 25 Mar 2021 18:26:08 -0400
Message-ID: <605D0DFF.3050905@isdg.net>
Date: Thu, 25 Mar 2021 18:26:07 -0400
From: Hector Santos <hsantos@isdg.net>
Reply-To: hsantos@isdg.net
Organization: Santronics Software, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.8.1
MIME-Version: 1.0
To: dmarc@ietf.org
References: <F1E2D8D7-9978-4C4B-9FD7-AB6428D12789@contoso.com> <20210324202058.91E777134D1B@ary.qy> <CABuGu1ovwwwwZALDOed74nBu1gOHcom8W+UDKC2GdWiEE_7yKw@mail.gmail.com> <4677E791-B028-4CAC-9752-0F4D8F1B0103@mimecast.com> <2ea2767-4940-77d1-e09e-a0ab215f9c9e@taugh.com>
In-Reply-To: <2ea2767-4940-77d1-e09e-a0ab215f9c9e@taugh.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/7aAF8_YJM1qyqHOndv9GsL8_pJM>
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: Thu, 25 Mar 2021 22:26:16 -0000

On 3/25/2021 2:23 PM, John R Levine wrote:
> While I am not opposed to a future tweak to DMARC to add some way to 
> say
> that A can sign for B, even if we did it, it would be a long time if 
> ever
> that DMARC verifiers implement it.  RFC 6541 added a third-party 
> signature
> option to DKIM in 2012, and after nine years, nobody implements it. 


Wildcat! SMTP implements RFC6541 "Authorized Third Party Signature" 
(ATPS)/ I'm sure I am not the only one and/or others have the options 
to enable it.

There are wizard for ADSP+ATPS and DMARC+ATPS:

https://secure.winserver.com/public/wcADSP
https://secure.winserver.com/public/wcDMARC

It works in proving the assertion by a 1st party Author Domain 
authorization for the existence of a specific 3rd party signer domain 
signature. Results are stamped in "Authorization-Results" header.

Add "atps=1" to your DMARC record and create a ATPS record to 
authorize 3rd party signature domains.

These domains are authorized to resign mail for the domain isdg.net

jchjykxmwknbyfge2bg4td6add264olh._atps TXT   ( "v=atps01; 
d=winserver.com;" )
kjshf2duqstols65zbhuytbbyr3zdecf._atps TXT   ( "v=atps01; d=gmail.com;" )
lykm653kj7yxeia665va7lszzthcx7jj._atps TXT   ( "v=atps01; 
d=beta.winserver.com;" )
pq6xadozsi47rluiq5yohg2hy3mvjyoo._atps TXT   ( "v=atps01; d=ietf.org;" )
tudfisabn5dz3vjm2kxcehc5attdbqh6._atps TXT   ( "v=atps01; 
d=santronics.com;" )

It can be managed like any other system.

This allows receivers to support a MAILING LIST that has resigned mail 
- the key problem we had since ADSP and now since DMARC because DMARC 
never bothered to even address the main concern with ADSP - the lack 
of a method to authorized a 3rd party.

ATPS offers it.

As to why the IETF.ORG mailing list does not support it or explore it 
and has chosen instead to rewrite, I don't know, but its so simple --- 
a DNS Lookup without any 5322.From tampering.

-- 
Hector Santos,
https://secure.santronics.com
https://twitter.com/hectorsantos