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

Scott Kitterman <sklist@kitterman.com> Thu, 15 June 2023 21:33 UTC

Return-Path: <sklist@kitterman.com>
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 0985FC15109D for <dmarc@ietfa.amsl.com>; Thu, 15 Jun 2023 14:33:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.097
X-Spam-Level:
X-Spam-Status: No, score=-7.097 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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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=kitterman.com header.b="DylKzyQs"; dkim=pass (2048-bit key) header.d=kitterman.com header.b="TvkbuUYK"
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 romIzFQR9S1Z for <dmarc@ietfa.amsl.com>; Thu, 15 Jun 2023 14:33:01 -0700 (PDT)
Received: from interserver.kitterman.com (interserver.kitterman.com [IPv6:2604:a00:6:1039:225:90ff:feaa:b169]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B5F06C151070 for <dmarc@ietf.org>; Thu, 15 Jun 2023 14:33:01 -0700 (PDT)
Received: from interserver.kitterman.com (interserver.kitterman.com [64.20.48.66]) by interserver.kitterman.com (Postfix) with ESMTPS id 010DBF802BA for <dmarc@ietf.org>; Thu, 15 Jun 2023 17:32:49 -0400 (EDT)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903e; t=1686864753; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from; bh=J4SBiv5DZkxzEBraGeAq/FDo5K9GuHmE7wsl1JQbg1o=; b=DylKzyQs4mKee6TfHPVimkFmU0L0s/47tG5KqbonX2pdTI7y8wLA2lD5SHGOWVJtcW8h3 43uYlG5Mo2vHo2FBA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903r; t=1686864753; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from; bh=J4SBiv5DZkxzEBraGeAq/FDo5K9GuHmE7wsl1JQbg1o=; b=TvkbuUYKxbj6eEp43HZMzD0TCTQn1u9D+6/54Lk2fhmgCCDPosmS101QFVKj/6MJkVK4q UuSHHjMtcB+zvd4vXinsEw0E6DYIIH8yalqd02Awi++kDFRMLLUqxbj/sAAbkAqahEm4smx ziz3PhGHsRZvKrngqoO/tj9P9Hf2XZcfJsSsXrnVY9Ed8WV/8kt9HycepoaXORiJ3IucQMn D4h2GlxS0pF3KV7+0br/erKqxgX9lQtxFaAvTMnMbAnsuHLHhyxJTZaBrQ9l2eyZD24Jwwe uwHwy+xsFmMQ4I7Irh/GCtDpNhKunmWPDFPmDBxuj74/K8XsRqsHjJV2ULjQ==
Received: from localhost.localnet (static-72-81-252-22.bltmmd.fios.verizon.net [72.81.252.22]) by interserver.kitterman.com (Postfix) with ESMTP id B9685F801FE for <dmarc@ietf.org>; Thu, 15 Jun 2023 17:32:33 -0400 (EDT)
From: Scott Kitterman <sklist@kitterman.com>
To: dmarc@ietf.org
Date: Thu, 15 Jun 2023 17:32:27 -0400
Message-ID: <8631997.xIE1f7fN3f@localhost>
In-Reply-To: <25736.57534.195344.782189@fireball.acr.fi>
References: <30BB83B2-B454-41B8-992B-8E2569802D9C@1und1.de> <CALaySJJbPFBAV_7mZaARYWuMzuX+74r2Cm0jD+z92_iuFRn_MQ@mail.gmail.com> <25736.57534.195344.782189@fireball.acr.fi>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/YggRgDsknHLHkRMx_4oTZON3n38>
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: Thu, 15 Jun 2023 21:33:06 -0000

On Tuesday, June 13, 2023 5:33:50 PM EDT Tero Kivinen wrote:
> Barry Leiba writes:
> > > DKIM only: ~99.5%
> > > DKIM + SPF: ~100%
> > > SPF only: ~100%
> > 
> > That's interesting and disturbing if it remains consistent.
> 
> The statistics I have are quite different. The failure rate is much
> bigger both in DKIM and SPF.
> 
> Following statistics is random subset of emails going through iki.fi
> system, from last 30 days, consisting bit less than 4 million emails.
> Iki.fi is email forwarding service, so about 90% of those emails will
> fail SPF checks after iki.fi sends them forward. DKIM will go through
> unmodified, and we do not modify normal messages (spam messages might
> get tagged as spam depending on the members configuration), so 85.75%
> of emails will still have valid DKIM signature after passing iki.

Thanks.  Sorry for the late reply, I've been tied up with some other work the 
last couple of days.

I'm not surprised it's radically different as it's a differently scoped data 
set.  As I mentioned up-thread these were for directly connected mail 
deliveries, so the normal DMARC failure mechanisms weren't relevant.  
Additionally, these were mail servers for domains which were actively working 
on having a complete/correct DKIM/SPF configuration to support DMARC, so not 
average in that manner either.

Since all we had were statistics based on DMARC feedback, we were never able 
to explore what was behind the DKIM failure rate.

Often in large entities, it's the compartmentalization and need for 
coordination that turns out to cause many of the problems.  I've worked with 
companies on DMARC deployments where helping them update or develop relevant 
internal policy, procedures, and processes ended up being a significant 
fraction of the effort.  SPF, DKIM, and DMARC introduce a requirement for a 
more centralized and complete view of outbound architecture than has 
historically been needed.

Scott K