Re: DMARC and ietf.org

Hector Santos <hsantos@isdg.net> Tue, 22 July 2014 17:28 UTC

Return-Path: <hsantos@isdg.net>
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 524361A002A for <ietf@ietfa.amsl.com>; Tue, 22 Jul 2014 10:28:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.001
X-Spam-Level:
X-Spam-Status: No, score=-102.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 o3J19ZCSB3-m for <ietf@ietfa.amsl.com>; Tue, 22 Jul 2014 10:28:11 -0700 (PDT)
Received: from pop3.winserver.com (secure.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id E4C901A0059 for <ietf@ietf.org>; Tue, 22 Jul 2014 10:28:10 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=2358; t=1406050081; h=Received:Received: Message-Id:From:Subject:Date:To:Organization:List-ID; bh=aeeHNnv VNq2fsreX9m08wf3GRkA=; b=pU92tDoJuma+EdRuoqXKwgNIZoP3SsuPgNy9YSo ylFl9AGSIPgw8DvPaPdCUw4DXzZu0sBWNTylJRuROf0UqJWNwYYzDWfITlcp8kNO 8OQZpZ+XoGqJ4VnEDJ9/qNowcnLCwfhBhMTtgJnXWJxOJohP8wC03Sflr9pY+DQL rOGk=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Tue, 22 Jul 2014 13:28:01 -0400
Received: from [192.168.1.221] (99-72-160-212.lightspeed.miamfl.sbcglobal.net [99.72.160.212]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 1235195731.1247.6128; Tue, 22 Jul 2014 13:28:01 -0400
References: <CAL0qLwYZPO9L9e7MHA6zP5vcTbQEJmwCSonLdMeQiOw4CUoiFw@mail.gmail.com> <20140718174827.652621ADAF@ld9781.wdf.sap.corp> <6.2.5.6.2.20140719235353.0c50d260@resistor.net> <25621.1405862805@sandelman.ca> <20140722133055.GY2595@mournblade.imrryr.org>
Mime-Version: 1.0 (1.0)
In-Reply-To: <20140722133055.GY2595@mournblade.imrryr.org>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Message-Id: <217BB698-278E-449C-B592-A74A4C69732F@isdg.net>
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-Mailer: iPad Mail (11B651)
From: Hector Santos <hsantos@isdg.net>
Subject: Re: DMARC and ietf.org
Date: Tue, 22 Jul 2014 13:28:00 -0400
To: "ietf@ietf.org" <ietf@ietf.org>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/0AdnlpGn93sHsj4GgdmqBXpfFmw
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, 22 Jul 2014 17:28:14 -0000

> On Jul 22, 2014, at 9:30 AM, Viktor Dukhovni <ietf-dane@dukhovni.org> wrote:
> 
>> On Sun, Jul 20, 2014 at 09:26:45AM -0400, Michael Richardson wrote:
>> 
>> Regardless of how/if/why/when we process DMARC as a specification, we need to
>> decide how ietf.org MTA is going to deal with things.
> 
> For what it is worth the postfix-users and postfix-devel mailing lists
> don't have any DMARC issues.  Long before DMARC, when DKIM was still
> an IETF draft, these lists were changed to not modify the message body
> or subject line in any way (no footers and no subject tags).

But this is a list service option.  I can't enforce one way or another for list operators to set their list up.  The default is to add a footer from a default template.  Can I change the default for future updates?   Sure, but that will violate a long term "no surprise" support principle for justifying automated updates (and the maintenance fees) and this would fall under a big surprise category.  

There are many list that desire the system level footer information, i.e. the note well for the IETF lists.   And I believe, needs to be double checked, there are some jurisdictions where is it legally required, i.e. CAN-SPAM.   The DMA I believe also expects it of it's member for community friendly spamming.  Overall, this is not something that can be universally applied.

> Rather, the lists only append "List-foo" headers, add a "Sender:"
> header and otherwise forward the original message unmodified with
> a new envelope.  The result is that the author DKIM signature
> remains valid if present.

In my assessment, this is a migration issue, restrictive domains need to be cleaned up from list databases.   More importantly, I think it is a mistake to try to kludge around a DMARC specification that is protocol-incomplete.  DMARC needs to get fixed first to support 3rd resigners and then we can better evaluate how a list system fits.  Right now, there are no options which has created a "chaotic hysteria" to rewrite authorship domains.  But even when fixed, at end of the day, there will always be restrictive domains with an ADMD mandate for exclusive mail domain operations and regardless of the amount,  their policies must be honored. 

--
Hector Santos
http://www.santronics.com