Re: [dmarc-ietf] Stats on DMARC adoption ?

Jim Fenton <fenton@bluepopcorn.net> Wed, 13 April 2022 21:25 UTC

Return-Path: <fenton@bluepopcorn.net>
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 BF5453A0864; Wed, 13 Apr 2022 14:25:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.109
X-Spam-Level:
X-Spam-Status: No, score=-2.109 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=bluepopcorn.net
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 GFZrhEeXRE_7; Wed, 13 Apr 2022 14:25:17 -0700 (PDT)
Received: from v2.bluepopcorn.net (v2.bluepopcorn.net [IPv6:2607:f2f8:a994::2]) (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 272FA3A085B; Wed, 13 Apr 2022 14:25:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bluepopcorn.net; s=supersize; h=Content-Transfer-Encoding:Content-Type: MIME-Version:References:In-Reply-To:Message-ID:Date:Subject:Cc:To:From:Sender :Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=PP0NpGmVBkUO6qDJZue+GlF9nb1YpR6r/LYwq2zM/Hg=; b=MXvVWcfOicEhaXE8mb5TYx4hig B9w1g7NpAiGUPzqljBF9cFvs2VfE0DLRRozgu2naDz05pkGQbUikS/N6p2HUqD9pS4AHnJ82mxLT9 StBq7tbNgLL7WqBiG+hv+v5zc3GRzvGFhzMNf+7cV4S7TbNCBsUZ5mcqx6QEqsjNw5Ks=;
Received: from [64.71.6.2] (helo=[10.100.11.204]) by v2.bluepopcorn.net with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from <fenton@bluepopcorn.net>) id 1nekUF-0005NW-R0; Wed, 13 Apr 2022 14:25:16 -0700
From: Jim Fenton <fenton@bluepopcorn.net>
To: Seth Blank <seth=40valimail.com@dmarc.ietf.org>
Cc: John Levine <johnl@taugh.com>, dmarc@ietf.org
Date: Wed, 13 Apr 2022 14:25:15 -0700
X-Mailer: MailMate (1.14r5852)
Message-ID: <68F43804-FB34-4DDF-9D4E-8547715CC180@bluepopcorn.net>
In-Reply-To: <CAOZAAfNm5Mkz4YBWOXWBzwNwkD=TujdQFQkYGV2bL7gZ66eFLQ@mail.gmail.com>
References: <20220413032759.0AEF93D48BB2@ary.qy> <CAOZAAfNm5Mkz4YBWOXWBzwNwkD=TujdQFQkYGV2bL7gZ66eFLQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/kb1aCSFeH_7QBYhrFisy2Wb_6N4>
Subject: Re: [dmarc-ietf] Stats on DMARC adoption ?
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: Wed, 13 Apr 2022 21:25:22 -0000

On 12 Apr 2022, at 20:39, Seth Blank wrote:

> Policies: https://dmarc.org/2022/03/dmarc-policies-up-84-for-2021/
>
> For mailboxes that implement DMARC and send reports, Valimail (and Dmarcian
> I believe) have historically tracked and published that. I'll hunt down
> that data tomorrow. Off the top of my head, it was about 80% of mailboxes
> globally (4bn+) properly validate DMARC, and the majority of those send
> reports, with the notable exception of Microsoft, which is now finally
> starting to do that.

Out of curiosity, what does “properly validate DMARC” mean and how do you measure it? If it means “retrieved the DMARC record”, that’s a metric but not all that meaningful. I run Spamassassin so I probably would be part of that metric but I’m not doing anything with the result. For that matter, Spamassassin used to retrieve ADSP records.

If, on the other hand, it means that the recipient domain is acting on a DMARC-published policy, that would be meaningful but I’m not sure how one would measure that.

-Jim