Re: [dmarc-ietf] DMARC2 & SPF Dependency Removal

Alessandro Vesely <vesely@tana.it> Fri, 09 June 2023 08:49 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 D7FFBC151709 for <dmarc@ietfa.amsl.com>; Fri, 9 Jun 2023 01:49:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.099
X-Spam-Level:
X-Spam-Status: No, score=-7.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_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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="Qa4S0XMv"; dkim=pass (1152-bit key) header.d=tana.it header.b="AdYmqhuP"
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id As-ZnEMhjIFt for <dmarc@ietfa.amsl.com>; Fri, 9 Jun 2023 01:49:10 -0700 (PDT)
Received: from wmail.tana.it (wmail.tana.it [94.198.96.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BCD5EC14CE5E for <dmarc@ietf.org>; Fri, 9 Jun 2023 01:49:09 -0700 (PDT)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=tana.it; s=epsilon; t=1686300547; bh=1DTVPYmJYvkNEHfmCjOniauvZSNEKOfwiiXngiGduRg=; h=Author:Date:Subject:To:References:From:In-Reply-To; b=Qa4S0XMvODxhkhtB0ZLDIi/OS2WB1iKNntT3LvIYrT/v9AI5r5tmy1YGYabLp/VgM kuxleiDUUsKkhvyhh4uCQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1686300547; bh=1DTVPYmJYvkNEHfmCjOniauvZSNEKOfwiiXngiGduRg=; h=Date:Subject:To:References:From:In-Reply-To; b=AdYmqhuPP95IjLhB5bfFdr9gyaUh0QnxmPWSahCTJDCZcliXBGgNjnAkLru/+E+PY Lx1Og9prdakX461v86jDkc3OCbqVZulo1U4vrc9/Auokzg90FjVWilWR0jiJF4Aoki PJ4Ag0NS/QaC2UwHCoV0NeQ5LHHeVkAEHu9jnuWqODC95yCOp/euEAc6/fv2r
Original-Subject: Re: [dmarc-ietf] DMARC2 & SPF Dependency Removal
Author: 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 00000000005DC05B.000000006482E782.00004F70; Fri, 09 Jun 2023 10:49:06 +0200
Message-ID: <7f854d28-d3b5-fd00-4613-b8baa1217bd7@tana.it>
Date: Fri, 09 Jun 2023 10:49:06 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.11.0
Content-Language: en-US, it-IT
To: dmarc@ietf.org
References: <30BB83B2-B454-41B8-992B-8E2569802D9C@1und1.de> <CAL0qLwbx6Y=kmB5pQZx8gNqD=rLBYz1vLOX6ngL=wUHHUm0Hjw@mail.gmail.com> <CAOZAAfMtsjcp+aCrwQ2QRc+SHsw3rhwMuTBugRYe44NeiMeKyg@mail.gmail.com> <CALaySJKrXJJXz3pgp85BPswoirhPJtD=uuefVfc9sX1fGkj-iA@mail.gmail.com>
Authentication-Results: tana.it; auth=pass (details omitted)
From: Alessandro Vesely <vesely@tana.it>
In-Reply-To: <CALaySJKrXJJXz3pgp85BPswoirhPJtD=uuefVfc9sX1fGkj-iA@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/lfCkhVQ9vrsbx4vjWmXjHbAOb2w>
Subject: Re: [dmarc-ietf] DMARC2 & SPF Dependency Removal
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.39
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: Fri, 09 Jun 2023 08:49:16 -0000

On Thu 08/Jun/2023 16:44:14 +0200 Barry Leiba wrote:
> See, I don't look at it as "harmed".  Rather, I think they're using "we use 
> SPF" as a *reason* not to use DKIM, and I think that *causes* harm.


Does that mean SPF is easier to enter than DKIM?  Maybe.  It can be an 
advantage, though.


> SPF is, as I see it, worse than useless, as it adds no value to domain that use 
> DKIM -- any time DKIM fails SPF will also fail -- and actually impedes the 
> adoption of DKIM.


I agree SPF is too much bloated by some providers, to the point that 
impersonation with dmarc=pass can be achieved programmatically.  However, I'd 
rather counter this using an extra spf=no tag, than v=DMARC2.  (Furthermore, 
I'd specify such extra tag in a separate document, not dmarcbis.)

One case I saw multiple times where DKIM fails while SPF verifies is when the 
message contains a line starting with "from " which some agent changes to 
">from ".  Some signing software eliminates such lines before signing, but 
that's not in the spec, so one cannot say a signer is defective if it doesn't 
do it.

What I find nonsensical is to eliminate SPF in order to save DNS queries, given 
that we replaced local PSL lookups with a series of queries.  We cannot do that 
and pretend that SPF is too expensive.


Best
Ale
--