Re: Will mailing lists survive DMARC?

Andrew Sullivan <ajs@anvilwalrusden.com> Tue, 29 April 2014 12:45 UTC

Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 48C191A08C3 for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 05:45:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.345
X-Spam-Level: *
X-Spam-Status: No, score=1.345 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FAKE_REPLY_C=1.486, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311] autolearn=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 8FKJSEsF2ESe for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 05:45:34 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 657D61A075D for <ietf@ietf.org>; Tue, 29 Apr 2014 05:45:34 -0700 (PDT)
Received: from mx1.yitter.info (69-165-131-253.dsl.teksavvy.com [69.165.131.253]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id A1B108A031 for <ietf@ietf.org>; Tue, 29 Apr 2014 12:45:32 +0000 (UTC)
Date: Tue, 29 Apr 2014 08:45:28 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: Will mailing lists survive DMARC?
Message-ID: <20140429124528.GA1324@mx1.yitter.info>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <0B08F94B-FD02-462F-9E74-E6CE7F85ECC9@frobbit.se> <alpine.DEB.2.02.1404291317510.29282@uplift.swm.pp.se>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/I4dxuKtshfEGuCYozBthvNKd530
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 29 Apr 2014 12:45:35 -0000

On Tue, Apr 29, 2014 at 01:22:31PM +0200, Mikael Abrahamsson wrote:

> I would really like to see the standards process for this mechanism
> be stopped 

Since it's an ISE stream document and its intended status is
"Informational", there is no standards process.  (If one thinks, "Yes,
but everyone treats RFCs as standards," then that's a different
discussion to the current one.)


On Tue, Apr 29, 2014 at 01:28:38PM +0200, Patrik Fältström wrote:
> 
> I ask myself as well what the problem is.
> 
> If there was collateral damage on third parties, that would for me have been a different thing. 

The issue is that the operators in this case are externalizing their
problem.  The operator makes the decision and establishes a policy
that causes mailing list postings from addresses inside the operator's
domain of control to bounce.  The person who has to cope with those
bounces is the mailing list manager, and _not_ the mail domain
operator.  The cost of the side effect is not actually borne by the
mail domain operator.  So there certainly is damage to someone other
than the operator of the mail domain (or its customers).

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com