IETF Logo Mail Archive

yet more DMARC stuff, was Re: Mailing list membership.

"John Levine" <johnl@taugh.com> Wed, 01 March 2017 21:00 UTC

Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 90EDA1296B2 for <ietf@ietfa.amsl.com>; Wed, 1 Mar 2017 13:00:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.821
X-Spam-Level:
X-Spam-Status: No, score=-0.821 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_DYNAMIC=1.08, SPF_PASS=-0.001] autolearn=no autolearn_force=no
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 RYpaUnvY1S4S for <ietf@ietfa.amsl.com>; Wed, 1 Mar 2017 13:00:56 -0800 (PST)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 596EF12967C for <ietf@ietf.org>; Wed, 1 Mar 2017 13:00:56 -0800 (PST)
Received: (qmail 82694 invoked from network); 1 Mar 2017 21:00:55 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 1 Mar 2017 21:00:55 -0000
Date: Wed, 01 Mar 2017 21:00:33 -0000
Message-ID: <20170301210033.1672.qmail@ary.lan>
From: John Levine <johnl@taugh.com>
To: ietf@ietf.org
Subject: yet more DMARC stuff, was Re: Mailing list membership.
In-Reply-To: <70ebe3f4-bae5-7b65-a8ba-b90fdc38dbb8@comcast.net>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/w-jWe83CRkoxKIeYdtG2h_UTDYc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Mar 2017 21:00:58 -0000

In article <70ebe3f4-bae5-7b65-a8ba-b90fdc38dbb8@comcast.net> you write:
>> This is a good idea.  Taking it a step further, perhaps a warning could be included when
>subscribing to an IETF list from an email provider who is known to use DMARC.

You can tell who publishes DMARC policies, but without experimentation
you can't tell who follows them on inbound mail.

Of the large public mail providers, only AOL and Yahoo currently
publish DMARC policies, but Gmail certainly looks at DMARC, albeit as
part of the special sauce so a Gmail user might get mail with DMARC
problems or might not.  I'm reasonably sure that Hotmail and Comcast
also look at DMARC on incoming mail.  DMARC is surprisingly useful for
blocking phishes, which is a big issue for consumer mail providers, so
the providers that use it are not going to stop.

R's,
John

PS: I presume you all know that we've been working on workarounds.

v2.23.0 | Report a Bug | By Email