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

Alessandro Vesely <vesely@tana.it> Fri, 09 June 2023 15:34 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 B8427C14CE38 for <dmarc@ietfa.amsl.com>; Fri, 9 Jun 2023 08:34:54 -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="KORlntah"; dkim=pass (1152-bit key) header.d=tana.it header.b="Bv/ZMvSZ"
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 20cvJI77ggqd for <dmarc@ietfa.amsl.com>; Fri, 9 Jun 2023 08:34:47 -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 E027AC1522A4 for <dmarc@ietf.org>; Fri, 9 Jun 2023 08:34:42 -0700 (PDT)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=tana.it; s=epsilon; t=1686324878; bh=0gM398NrHpGVTP28ed5KEaxpuXiqMKzDDKPhpxNtpmk=; h=Author:Date:Subject:To:Cc:References:From:In-Reply-To; b=KORlntahZ0+YBTsDV+K68HcBmU0FA+AF+jCbpcI11Oc3KQ0pxbjqa0PhmszZHOXmI I04NArCZicJxx86Tnq+Dg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1686324878; bh=0gM398NrHpGVTP28ed5KEaxpuXiqMKzDDKPhpxNtpmk=; h=Date:Subject:To:Cc:References:From:In-Reply-To; b=Bv/ZMvSZMu2vqakXFsWdqEctQyYKKFmc0ZM+chLK0GJsgrZ0iXLPyzHklM591VPtk 3Fe1qi2UeCUUmDAQXrXXf0+dNo6hQZOT70GNrCEMJbBlb9JO3n6YaOjwjX3fvN0r7f YBt//P5cU8tim/QW1JCmWjtvCNTahOxg9breppdiKN33YUObrFneReknOfjL/
Original-Subject: Re: [dmarc-ietf] DMARC2 & SPF Dependency Removal
Author: Alessandro Vesely <vesely@tana.it>
Original-Cc: dmarc@ietf.org
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 00000000005DC0BC.000000006483468E.000022D5; Fri, 09 Jun 2023 17:34:38 +0200
Message-ID: <98b81938-7744-2bd6-7fd1-81125a71247b@tana.it>
Date: Fri, 09 Jun 2023 17:34:38 +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: Barry Leiba <barryleiba@computer.org>
Cc: 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> <7f854d28-d3b5-fd00-4613-b8baa1217bd7@tana.it> <CALaySJLeJ0xproB6Eg-37sSrNS7XrewUmdKZYVPsVeWddJ90MQ@mail.gmail.com>
Authentication-Results: tana.it; auth=pass (details omitted)
From: Alessandro Vesely <vesely@tana.it>
In-Reply-To: <CALaySJLeJ0xproB6Eg-37sSrNS7XrewUmdKZYVPsVeWddJ90MQ@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/6An54cf2cCY-lt_XjIhaTYa8UAg>
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 15:34:54 -0000

On Fri 09/Jun/2023 11:14:29 +0200 Barry Leiba wrote:
>> 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.
> 
> Have you seen that happen in the MTA relay process (in transit), or
> only after final delivery?  I can see that an MDA or a recipient MUA
> might do that, but it should *not* happen in transit, so it shouldn't
> affect DMARC processing.  Do you have actual examples where an MTA is
> making that change and breaking the DKIM sig?


I recall it was a problem, which is why I coded the replacement (I add a space, 
not a '>').  In the early years, DKIM suffered mime-autoconversions that many 
MTA were applying just for fun.  And there were some other corner cases that 
now defeat my recollection.

Anyway, having a second string at one's bow is not a defect, unless it's set up 
in a defective way.  But also DKIM can be misconfigured, which is not a good 
reason to eliminate it.  Having both increases the chances of success.


Best
Ale
--