Re: [dmarc-ietf] Ticket #1 - SPF alignment

Alessandro Vesely <> Thu, 21 January 2021 09:24 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 69A973A185A for <>; Thu, 21 Jan 2021 01:24:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.382
X-Spam-Status: No, score=-2.382 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.262, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1152-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id ug9TOiXEb_o3 for <>; Thu, 21 Jan 2021 01:24:28 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id B6AE83A0D25 for <>; Thu, 21 Jan 2021 01:24:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=delta; t=1611221064; bh=gl1SdCn87GoxgJwc0KgvYY/a28dg8vl1nq++e1erN8c=; l=1433; h=To:References:From:Date:In-Reply-To; b=AjKlKQ9M7Q3ZFSO44EEh3kIAvkVCX8u1mOL2tupGV91xv3/dtmMbr0uKCZphF1McP u/KkuvKYzR0b7W6PeSbl6FnFJvhRTIosEnT+sykAaEzHjqs6QI9xXL4xUUNWTt5MFy tIzkDObKg5bdNUivRGR+h5bFlibOEN1CYrNlbJp4wpPZQ/aipsb4TdPwz2JUU
Authentication-Results:; auth=pass (details omitted)
Original-From: Alessandro Vesely <>
Received: from [] (pcale.tana []) (AUTH: CRAM-MD5 uXDGrn@SYT0/k, TLS: TLS1.3, 128bits, ECDHE_RSA_AES_128_GCM_SHA256) by with ESMTPSA id 00000000005DC056.0000000060094847.000070CD; Thu, 21 Jan 2021 10:24:23 +0100
References: <> <> <> <>
From: Alessandro Vesely <>
Message-ID: <>
Date: Thu, 21 Jan 2021 10:24:22 +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: <>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <>
Subject: Re: [dmarc-ietf] Ticket #1 - SPF alignment
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 21 Jan 2021 09:24:30 -0000

On Tue 19/Jan/2021 22:26:09 +0100 Todd Herr wrote:
> Picking up the thread on another ticket that was brought before the group
> pre-holidays and has lain fallow since the end of 2020...
> John Levine asserted that there wasn't a lot of strong opinion on the
> matter, and therefore we'd be leaving the spec as is, with the MAIL FROM
> SPF check the only one that matters for DMARC.
> Ale replied, but I don't interpret his reply as challenging John's
> assertion.

The thread went off-topic w.r.t. the purpose of ticket #1.

> Can this ticket be closed?

I agree that the spec needs some text somewhere to counter the passage in 
Section 2.3 of RFC 7208.  This, methinks, is the intended semantics of the 
second paragraph of section 3.1.2 of dmarcbis:

    Note that the RFC5321.HELO identity is not typically used in the
    context of DMARC (except when required to "fake" an otherwise null
    reverse-path), even though a "pure SPF" implementation according to
    [RFC7208] would check that identifier.

I'd rather replace that paragraph and leave item 4 of Section 6.6.2 as is.  For 
a possibly less confusing wording:


    Even tough a "pure SPF" implementation, according to [RFC7208], would
    avoid to check the RFC5321.MailFrom identity if the RFC5321.HELO was
    conclusively determined to pass, DMARC authentication requires the
    authenticated identity to be aligned.