Re: Will mailing lists survive DMARC?

Mikael Abrahamsson <swmike@swm.pp.se> Tue, 29 April 2014 11:22 UTC

Return-Path: <swmike@swm.pp.se>
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 804B71A0858 for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 04:22:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.002
X-Spam-Level:
X-Spam-Status: No, score=-4.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_SE=0.35, J_CHICKENPOX_16=0.6, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
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 iy4y_rcLpaTe for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 04:22:33 -0700 (PDT)
Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) by ietfa.amsl.com (Postfix) with ESMTP id 4C1C61A083B for <ietf@ietf.org>; Tue, 29 Apr 2014 04:22:33 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 87BD3A5; Tue, 29 Apr 2014 13:22:31 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1398770551; bh=/wyOCbXQ8wSveISyyR9+msDScELhSyUolXBkDuu4Q7M=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=LMWiIU0uDgrZhGtq7p4hqFozLsXTbJMmkuvzY0/G0U0/oGAZXKm6CU23Sa5/aQsGD rqL3SLm+whf2t0q911tZdNumR1JYlPdDRUJ812KMD8XUTuSbDSN8oVL2XHI5EV9bkN +x5PkBIR7Wwl++rJXnEDqrAkVRcaDnGCG0Mrn3tk=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 7E9DDA2; Tue, 29 Apr 2014 13:22:31 +0200 (CEST)
Date: Tue, 29 Apr 2014 13:22:31 +0200
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Alessandro Vesely <vesely@tana.it>
Subject: Re: Will mailing lists survive DMARC?
In-Reply-To: <535F88C3.4060002@tana.it>
Message-ID: <alpine.DEB.2.02.1404291317510.29282@uplift.swm.pp.se>
References: <535F88C3.4060002@tana.it>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/emueak90oTwYnN89lK8JrVfYvNM
Cc: ietf <ietf@ietf.org>
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 11:22:35 -0000

On Tue, 29 Apr 2014, Alessandro Vesely wrote:

> There has been some discussion on what should the IETF do about the
> collateral damage experienced by several mailing lists when major
> mailbox providers switch their DMARC policies to p=reject.
>
> Mailing lists used to be a legitimate use of email.  Albeit they are
> the workhorse of many organizations which are vital for the Internet
> itself, such as the IETF and several software projects, statistically
> they are a minor Internet feature.  I can understand that after
> decades of failed attempts to control email abuse, their disappearance
> is not the main concern of "p=reject" proponents.

Actually, I can't. Not fixing the mailing list and calling it "collateral 
damage but that's ok" is for me totally out of the question. On the other 
hand, this will primarily cause direct problems to users/customers of the 
organisations that decide to do "p=reject" as their participation in 
mailing lists will be crippled.

> The DMARC draft is currently in "AD Followup" state.  A review was
> posted here last week, a process which doesn't seem to affect
> deployment much.
>
> How is the IETF going to proceed on this issue?

I would really like to see the standards process for this mechanism be 
stopped until the mailing list problem has been sorted out. I don't really 
understand how it got that far with this problem unsolved.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se