DMARC: perspectives from a listadmin of large open-source lists

"Robin H. Johnson" <> Tue, 08 April 2014 03:35 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 34B3C1A00BC for <>; Mon, 7 Apr 2014 20:35:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.412
X-Spam-Status: No, score=-4.412 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, J_CHICKENPOX_55=0.6, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id fNEqV6UDGLWn for <>; Mon, 7 Apr 2014 20:35:42 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 9F64D1A00AE for <>; Mon, 7 Apr 2014 20:35:42 -0700 (PDT)
Received: from (localhost []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 1C67933FF8A for <>; Tue, 8 Apr 2014 03:35:36 +0000 (UTC)
Received: (qmail 28305 invoked by uid 10000); 8 Apr 2014 03:35:32 -0000
Date: Tue, 08 Apr 2014 03:35:32 +0000
From: "Robin H. Johnson" <>
Subject: DMARC: perspectives from a listadmin of large open-source lists
Message-ID: <>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="AsKt9WDFSpw8OJmf"
Content-Disposition: inline
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Mailman-Approved-At: Tue, 08 Apr 2014 08:48:29 -0700
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 08 Apr 2014 03:37:56 -0000


I'm the listadmin (amongst other things) for Gentoo Linux. Our lists
handle somewhere north of 100k deliveries/day; it's a large deployment
of mlmmj.

I also happen to personally host the lists for my local hackerspace, and
that's where I first noticed DMARC causing problems, because one of our
members activated reject mode on his personal domain, and then all
yahoo+gmail recipients started having bounced mail whenever mail from
the DMARC-progressive user was sent.

I wrote up my findings here:

If the listserv's outgoing MTA does implement DKIM signing, this problem
will still occur because it's legitimately valid for the From header to
differ from the envelope sender. That's why the extra DMARC header
X-Original-Authentication-Results [1] is needed sadly :-(.

The problem described WILL vanish when all mailing list apps implement
DMARC, but until then, it's really broken.

It's really bad because not a single list implementation supports DMARC
yet; mailman is the closest, but still not yet there.

If possible, if everybody could highlight the lack of open-source
support for DMARC in list apps, that would be hugely beneficial to the

At the same time, delaying mass usage of the reject policy would limit


Robin Hugh Johnson
Gentoo Linux: Developer, Infrastructure Lead
E-Mail     :
GnuPG FP   : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85