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

Seth Blank <seth@valimail.com> Thu, 14 April 2022 03:54 UTC

Return-Path: <seth@valimail.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 539D83A101F for <dmarc@ietfa.amsl.com>; Wed, 13 Apr 2022 20:54:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.108
X-Spam-Level:
X-Spam-Status: No, score=-7.108 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, 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 (2048-bit key) header.d=valimail.com
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 G5pfcRTmJ5-N for <dmarc@ietfa.amsl.com>; Wed, 13 Apr 2022 20:54:45 -0700 (PDT)
Received: from mail-vk1-xa2f.google.com (mail-vk1-xa2f.google.com [IPv6:2607:f8b0:4864:20::a2f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8620E3A101E for <dmarc@ietf.org>; Wed, 13 Apr 2022 20:54:45 -0700 (PDT)
Received: by mail-vk1-xa2f.google.com with SMTP id 80so1564576vkw.0 for <dmarc@ietf.org>; Wed, 13 Apr 2022 20:54:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=valimail.com; s=google2048; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Zu16T7L7Rfk+mDwOEqxROJCm+wBwE7KYxPSFaOOmpbU=; b=D1VPvMuW4B8Xwfiqp4ndku+Cf1JB4r1FMAYAxTPJW3rojjpjNWs2Ba4vWEv46cgY2/ tOLB3ml+K707bRV6D6cSLyj8dCCYMR1NUQ8wHfB3PBdAhNLLcqVLOjyM6kHUBOnnHRso /Az1yl/PcC6Oi0f06ZrFSs+sm+meIvlw8lXxPJo8i89sHyRYqsgEWxT29CZ1POXIJtzx kcKTDyLqEeukVmfUTegB9mtlAyoBFRVE7R+LbuXi+M9QMSBGa5lna1RBsa7bMvkpFC7j CB3EyiFZZYbqhuGYl54uJhMaKv5uioEWTIDWkkFrjSWycP475MYHQW4lqo7B0RCZoFuH dh+g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Zu16T7L7Rfk+mDwOEqxROJCm+wBwE7KYxPSFaOOmpbU=; b=afHzm5mZ//Sx1xISqDcEbKYRT5Yl9VxOqmGRxTEB7L95ohYFF7kOkuujXJ+eUAEYRf E6wAqxssbfAzM0Pu/WMpz2RtAMtpmd1NJ4R09Gbyn5sVd8s+vCi9FuJjEgfe8WG3I3AV CPLfTCVLeieqGQMj3ZFRqF/ftQmh34GXEddUE7Iy2dEX1ypJKCN3uwp2e37CCuVj/6PN n2ANchQidzIYJg2C7lTlecVJ53jSPQPkbp2oYLtoUM4+KaBFsJIAI1MSHC0G1GwdEDaz 2Gv8yTRMzgZNMYgD16nEIVO1jcvwhScFhQt4FWZqk35Bi5ObLb4w9/tEpPMEUPHP2JCk lvXA==
X-Gm-Message-State: AOAM531l0tiecLar/zpRtrkAoa28tqvhkoIkhplIpxeG4KDuOnsgcI8W lYqNihR7wW8rTmRPSuzkjrLLVPpYOyBKfgMToAVkbQLvcUM=
X-Google-Smtp-Source: ABdhPJxvNv7FVIBuoWQJpMoFW+JlB86xKfyJyge2gtWFWN7U1EX5bW1WjZfDkNLQgPHTt+tHz2zKPoz14TSotZoxFbY=
X-Received: by 2002:a05:6122:98c:b0:345:9296:cee8 with SMTP id g12-20020a056122098c00b003459296cee8mr839852vkd.3.1649908484006; Wed, 13 Apr 2022 20:54:44 -0700 (PDT)
MIME-Version: 1.0
References: <20220413032759.0AEF93D48BB2@ary.qy> <CAOZAAfNm5Mkz4YBWOXWBzwNwkD=TujdQFQkYGV2bL7gZ66eFLQ@mail.gmail.com> <68F43804-FB34-4DDF-9D4E-8547715CC180@bluepopcorn.net>
In-Reply-To: <68F43804-FB34-4DDF-9D4E-8547715CC180@bluepopcorn.net>
From: Seth Blank <seth@valimail.com>
Date: Wed, 13 Apr 2022 20:54:32 -0700
Message-ID: <CAOZAAfOkF6RUuxaRc-Qkq=new_FxKmMEj=eHo0=CwSTe34Gdiw@mail.gmail.com>
To: Jim Fenton <fenton@bluepopcorn.net>
Cc: John Levine <johnl@taugh.com>, dmarc@ietf.org
Content-Type: multipart/alternative; boundary="00000000000019fa8f05dc9541b3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/LhmVD1rTWHbcT8L-DISD8FAECjs>
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: Thu, 14 Apr 2022 03:54:51 -0000

On Wed, Apr 13, 2022 at 2:25 PM Jim Fenton <fenton@bluepopcorn.net> wrote:

> 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.
>

Yes, "properly validates DMARC" means the mailbox provider validates and
handles the message per RFC 7489. This is easy to measure, because there
aren't that many large mailbox providers, and most are a) public with how
many mailboxes they represent, b) public with the fact that they validate
DMARC, and c) (in nearly all the cases, sans Microsoft) send reports which
can be used to confirm the proper handling of messages per published policy.

S


>
> -Jim
>


-- 

*Seth Blank * | Chief Product Officer
*e:* seth@valimail.com
*p:* 415.273.8818

This email and all data transmitted with it contains confidential and/or
proprietary information intended solely for the use of individual(s)
authorized to receive it. If you are not an intended and authorized
recipient you are hereby notified of any use, disclosure, copying or
distribution of the information included in this transmission is prohibited
and may be unlawful. Please immediately notify the sender by replying to
this email and then delete it from your system.