Re: [dmarc-ietf] auth-res vs. dmarc

Alessandro Vesely <vesely@tana.it> Wed, 30 December 2020 08:58 UTC

Return-Path: <vesely@tana.it>
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 922573A02BD for <dmarc@ietfa.amsl.com>; Wed, 30 Dec 2020 00:58:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, RCVD_IN_MSPIKE_H3=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 (1152-bit key) header.d=tana.it
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 o0eGfwyAO6Ev for <dmarc@ietfa.amsl.com>; Wed, 30 Dec 2020 00:58:03 -0800 (PST)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) (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 4AD853A017E for <dmarc@ietf.org>; Wed, 30 Dec 2020 00:58:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1609318679; bh=thOC9ukdPq3TFCzK6wrCiduFgWmyJejy1EpOHWYO6EA=; l=446; h=To:References:From:Date:In-Reply-To; b=AyO8QyyAwHKyooBR8sHSRrtG4oajPwPrikTRmYKuSxR04IYc5e1EZEXAo+u1xUoap pSoYP2Zcaayp+Tnr4KTy3iVMQ1HpIgEAN6VmfGbs0CA67U3xiPAyWdezltuKIeGE0B yvqxIBwsbPiSN+CaY0OpyxufNJsTyJCDpF6s2oJ92qleW9owqvsFEGgdTd9fd
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
Received: from [172.25.197.111] (pcale.tana [172.25.197.111]) (AUTH: CRAM-MD5 uXDGrn@SYT0/k, TLS: TLS1.3, 128bits, ECDHE_RSA_AES_128_GCM_SHA256) by wmail.tana.it with ESMTPSA id 00000000005DC053.000000005FEC4117.000022DC; Wed, 30 Dec 2020 09:57:59 +0100
To: dmarc@ietf.org
References: <9f6782b1-e85b-1a9c-9151-98feff7e18ea@mtcc.com> <CAHej_8m0OWsTt+tcSgUh+Fxu=HH_57nsb2O1Q_fgA2453ceh4g@mail.gmail.com> <140485eb-020f-4406-3f2f-e2c475ea51e5@mtcc.com> <CAHej_8mApfoF2ORgL+DoYTanrdhMjvT9H27kORwLKCQc1C9sRw@mail.gmail.com> <5588dbbe-b876-ed80-c80f-792380e3718f@mtcc.com> <CAHej_8=kW_t_JkOxUud1Uz8+PrbMh5CfwfxZK=mhe0wjW8wQpw@mail.gmail.com> <54dd9978-bcd1-6757-ad27-dcef6db6e5f7@mtcc.com> <CAHej_8kCi=7oqojDH_rbjn7kRg-PTDJWLgcKTGK9z-baUnKeMw@mail.gmail.com> <ef32de1e-d47e-1d0f-3cec-5994c7fdb7ae@mtcc.com> <CAH48ZfyxXz-2Wpwmzi+mW_KSS0aS06+yiEOk3YB_UrOKdcsQjA@mail.gmail.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <ceb55491-d11b-57c0-3d40-9188b06dbeb7@tana.it>
Date: Wed, 30 Dec 2020 09:57:57 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <CAH48ZfyxXz-2Wpwmzi+mW_KSS0aS06+yiEOk3YB_UrOKdcsQjA@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/jmc9d5UNEa6gFyA6WW0WSZZmHWU>
Subject: Re: [dmarc-ietf] auth-res vs. dmarc
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, 30 Dec 2020 08:58:05 -0000

On Wed 30/Dec/2020 02:30:40 +0100 Douglas Foster wrote:
> DKIM, A-R, and ARC should all have a mandatory attribute indicating the HELO 
> name of the server applying the header, the IP Address of the previous server 
> which supplied the information being evaluated, or both.


For DKIM, the HELO name is irrelevant.  d= determines who did the deed.

A-R and ARC have an authserv-id which is often consistent with HELO.


Best
Ale
--