IETF Logo Mail Archive

[dmarc-ietf] DMARC Coverage

Scott Kitterman <sklist@kitterman.com> Sat, 13 April 2019 21:12 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 90B6212030F for <dmarc@ietfa.amsl.com>; Sat, 13 Apr 2019 14:12:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_FAIL=0.001, SPF_PASS=-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=vZqm+jDI; dkim=pass (2048-bit key) header.d=kitterman.com header.b=PmikKL1r
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 E8_WOUmEJa2z for <dmarc@ietfa.amsl.com>; Sat, 13 Apr 2019 14:12:26 -0700 (PDT)
Received: from interserver.kitterman.com (interserver.kitterman.com [IPv6:2604:a00:6:1039:225:90ff:feaa:b169]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1C40A12026B for <dmarc@ietf.org>; Sat, 13 Apr 2019 14:12:25 -0700 (PDT)
Received: from interserver.kitterman.com (interserver.kitterman.com [64.20.48.66]) by interserver.kitterman.com (Postfix) with ESMTPS id 0CAC9F807E8 for <dmarc@ietf.org>; Sat, 13 Apr 2019 17:12:24 -0400 (EDT)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903e; t=1555189943; h=from : to : subject : date : message-id : mime-version : content-transfer-encoding : content-type : from; bh=xm17an4AqrcNOHQ4e/+kaSY4QXr7WrxR8eVNK+zErbg=; b=vZqm+jDIWlLfdIrymwxoR3cTeSfhqmPO1X7fWTNoT2Fn8+6aUSvANrEU EARTMVFiPjz++uEW1bCkPmZx+770AQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903r; t=1555189943; h=from : to : subject : date : message-id : mime-version : content-transfer-encoding : content-type : from; bh=xm17an4AqrcNOHQ4e/+kaSY4QXr7WrxR8eVNK+zErbg=; b=PmikKL1rK55ECth1pcOUE1rgE5DTm9KVCe8ClCC7hyETNS5v9R7APHvI 6aQSSDWEhIiFyZEDLVvSNA7AA2KooQAzUmKM60VkknvXKm7mIbZl+Ds9YG JzgSm8cvjmgigcfrbw7/1LFQP0Orgm6q2RBROIqM8sBMalPpff1rfLrHNh F4d3l2M7mQDzg9hDuNcwYRYaIbOBzh2OFLpIEAFnaO4FO1D4PAKJ7bmphf +7Mcj50DJ+XxNJCuhMn0j65DpOCQDclExuajANjot4tEsfR/ObTIUD6SWl nSv9xuHel8tNEpgocv3xgStpXdRzVjD322Bq88/Vc5Q1elCNhqXHSw==
Received: from kitterma-e6430.localnet (static-72-81-252-22.bltmmd.fios.verizon.net [72.81.252.22]) by interserver.kitterman.com (Postfix) with ESMTPSA id CDDFAF807E3 for <dmarc@ietf.org>; Sat, 13 Apr 2019 17:12:23 -0400 (EDT)
From: Scott Kitterman <sklist@kitterman.com>
To: dmarc@ietf.org
Date: Sat, 13 Apr 2019 17:12:20 -0400
Message-ID: <8060835.KeXT7UZBJi@kitterma-e6430>
User-Agent: KMail/4.13.3 (Linux/3.13.0-164-generic; KDE/4.13.3; x86_64; ; )
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/m8JMzezgWHdQubxmEnR8XQCg4CQ>
Subject: [dmarc-ietf] DMARC Coverage
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: Sat, 13 Apr 2019 21:12:27 -0000

A couple of days ago I sent a single message to a reasonably large mailing 
list (spf-help, email oriented - so likely not representative, but it's a data 
point).  Since I am a list owner, I know how many subscribers there are and 
from my DMARC feedback, I know how many times that single message got 
reported.

43% of them showed up in my DMARC feedback, so that's at least one data point 
on breadth of coverage for DMARC feedback.

To do this (at least the way I did it), you need to send a single message in a 
reporting period to an email list that does not re-write from and for which 
you know how many subscribers there are.

I'm curious what kind of numbers other might be able to come up with.

Scott K

v2.23.0 | Report a Bug | By Email