Re: [dmarc-ietf] Best Guess SPF should not be deprecated.
Alessandro Vesely <vesely@tana.it> Mon, 06 December 2021 19:01 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 30D0F3A0DDE for <dmarc@ietfa.amsl.com>; Mon, 6 Dec 2021 11:01:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.95
X-Spam-Level:
X-Spam-Status: No, score=-3.95 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=-1.852, 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=neutral reason="invalid (unsupported algorithm ed25519-sha256)" header.d=tana.it header.b=NwociXp2; dkim=pass (1152-bit key) header.d=tana.it header.b=A0ryqX2E
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 cV4G6GOGCUpt for <dmarc@ietfa.amsl.com>; Mon, 6 Dec 2021 11:01:25 -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 255103A0DD3 for <dmarc@ietf.org>; Mon, 6 Dec 2021 11:01:13 -0800 (PST)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=tana.it; s=epsilon; t=1638817270; bh=M+YuoWfpmxjI2EEvpglNB+DU17lwbArnQt2o2RwxsX8=; h=Subject:To:References:From:Date:In-Reply-To; b=NwociXp2dhxMM70Ieq/e8ZYDjOLUj4yEwQYRGuH5kxNotprAri8xuQXX5vaR6ZxI5 gJfn01k8urURFYNDfzxCQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1638817270; bh=M+YuoWfpmxjI2EEvpglNB+DU17lwbArnQt2o2RwxsX8=; h=To:References:From:Date:In-Reply-To; b=A0ryqX2ElHkOsZUYoth0/VcLD/fDVNsru3qbbd6mnNCMEsbQVS/Hy49c7GaQC+Z2k Rlda7uXF1H+1tNU55X4+yDLxqoFPxey5ocVYXn4B4mFHq5IZCTGYMRYv1ehAdPAupn VwGOMG3dRSpTYD5VKwNcdRtrre1xIm1Zy75lRbGOsqafPbNVLoEUN8X43XkWn
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 00000000005DC028.0000000061AE5DF6.00005679; Mon, 06 Dec 2021 20:01:10 +0100
To: dmarc@ietf.org
References: <CAH48Zfx4rvhG4ZbUmJtY32-+X=-9hxTdUbn0JT3pJ=5OYzkc2g@mail.gmail.com> <CAHej_8nCXfNkx6043YX5YkPG0XDOcapMO5j9qwSLJA_wqCQ2QA@mail.gmail.com> <80735575-AC99-4564-9A4D-A440DE62F584@kitterman.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <6c8b059e-2ab5-ea78-abd7-6e27c4cf6aab@tana.it>
Date: Mon, 06 Dec 2021 20:01:10 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0
MIME-Version: 1.0
In-Reply-To: <80735575-AC99-4564-9A4D-A440DE62F584@kitterman.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/QKMECj5dOtXxmh5-kvOxL6vAdHk>
Subject: Re: [dmarc-ietf] Best Guess SPF should not be deprecated.
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: Mon, 06 Dec 2021 19:01:35 -0000
On Mon 06/Dec/2021 14:29:02 +0100 Scott Kitterman wrote: > On December 6, 2021 1:04:44 PM UTC, Todd Herr <todd.herr@valimail.com> wrote: >>On Sat, Dec 4, 2021 at 5:35 PM Douglas Foster <dougfoster.emailstandards@gmail.com> wrote: >> >>> I have multiple objections to this paragraph in section 5.7.2 >>> >>> "Heuristics applied in the absence of use by a Domain Owner of either SPF >>> or DKIM (e.g., [Best-Guess-SPF <https://www.ietf.org/archive/id/draft-ietf-dmarc-dmarcbis-04.html#Best-Guess-SPF> >>> ]) SHOULD NOT be used, as it may be the case that the Domain Owner wishes >>> a Message Receiver not to consider the results of that underlying >>> authentication protocol at all." >>> >>> [snip] >>> >>> >>> I think this text was inserted because of an open ticket when discussion >>> was going nowhere and a new draft was created. Perhaps the originator of >>> that ticket can elaborate on his thinking. >>> >>> >>To be clear, the text at issue is present in RFC 7489, Section 6.6.2. >> >>That doesn't make it immutable, of course... > > Thanks for the clarification. I'd forgotten that was there. I definitely think it should be removed, regardless of the origin. I assume you said one can locally evaluate Best-Guess-SPF, but should not taint DMARC results by considering its outcome. That paragraph should then be left there, no? > In addition to my comments about leaving SPF best guess out, I think the DKIM part is problematic too. There really aren't any DKIM heuristics to use "in the absence of use by a domain owner". The only DKIM related heuristics that might apply to this section are the ones we've discussed about recovering signatures that failed due to in transit modification. Those are a good thing, even if they aren't broadly applicable enough to warrant standardization. Agreed. However, I wonder if there are heuristics for DMARC itself. Step 2 seems to suggest to skip any SPF or DKIM verification if no policy is found. By the same logic, it could even suggest to skip verifications if p=none and no rua/ ruf were found. Instead, IMHO, there's some value in carrying out verifications nonetheless. > I think what better goes in this spot is a more general comment about local policy (it doesn't seem to be discussed elsewhere). That would include mentioning ARC as an input to local policy. I have also suggested an appendix or possibly a separate document on things mail senders, intermediaries, and receivers can do to improve the reliability of DMARC through indirect mail flows. This would be one place that should be referenced. > > I'll provide text if people like the concept. IMHO that'd be interesting. Best Ale --
- [dmarc-ietf] Best Guess SPF should not be depreca… Douglas Foster
- Re: [dmarc-ietf] Best Guess SPF should not be dep… Murray S. Kucherawy
- Re: [dmarc-ietf] Best Guess SPF should not be dep… Dave Crocker
- Re: [dmarc-ietf] Best Guess SPF should not be dep… Scott Kitterman
- Re: [dmarc-ietf] Best Guess SPF should not be dep… Seth Blank
- Re: [dmarc-ietf] Best Guess SPF should not be dep… Scott Kitterman
- Re: [dmarc-ietf] Best Guess SPF should not be dep… Murray S. Kucherawy
- Re: [dmarc-ietf] Best Guess SPF should not be dep… Todd Herr
- Re: [dmarc-ietf] Best Guess SPF should not be dep… Scott Kitterman
- Re: [dmarc-ietf] Best Guess SPF should not be dep… Scott Kitterman
- Re: [dmarc-ietf] Best Guess SPF should not be dep… Alessandro Vesely
- Re: [dmarc-ietf] Best Guess SPF should not be dep… Scott Kitterman
- Re: [dmarc-ietf] Best Guess SPF should not be dep… Dave Crocker
- Re: [dmarc-ietf] Best Guess SPF should not be dep… Scott Kitterman
- Re: [dmarc-ietf] Best Guess SPF should not be dep… Dave Crocker
- Re: [dmarc-ietf] Best Guess SPF is a dead hack fr… John Levine
- Re: [dmarc-ietf] Best Guess SPF is a dead hack fr… Dave Crocker
- Re: [dmarc-ietf] Best Guess SPF is a dead hack fr… Scott Kitterman
- [dmarc-ietf] ARC's role, was Best Guess SPF shoul… Alessandro Vesely