IETF Logo Mail Archive

Re: DMARC and ietf.org

John Payne <john@sackheads.org> Mon, 18 July 2016 11:43 UTC

Return-Path: <john@sackheads.org>
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 1C01512D8BA for <ietf@ietfa.amsl.com>; Mon, 18 Jul 2016 04:43:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.187
X-Spam-Level:
X-Spam-Status: No, score=-3.187 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.287] autolearn=ham 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 1JGVMncaPdby for <ietf@ietfa.amsl.com>; Mon, 18 Jul 2016 04:43:27 -0700 (PDT)
Received: from chumdrop.sackheads.org (chumdrop.sackheads.org [159.203.76.21]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4067812D8F1 for <ietf@ietf.org>; Mon, 18 Jul 2016 04:43:15 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by chumdrop.sackheads.org (Postfix) with ESMTP id F3EFD14E02E; Mon, 18 Jul 2016 07:42:44 -0400 (EDT)
Received: from chumdrop.sackheads.org ([127.0.0.1]) by localhost (chumdrop.sackheads.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XiP-AoemW7CH; Mon, 18 Jul 2016 07:42:44 -0400 (EDT)
Received: from [192.168.1.63] (c-73-218-202-37.hsd1.ma.comcast.net [73.218.202.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: john@sackheads.org) by chumdrop.sackheads.org (Postfix) with ESMTPSA id C350414D628; Mon, 18 Jul 2016 07:42:44 -0400 (EDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_7D40EE2D-7D11-4BA6-818D-F168BE247683"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: DMARC and ietf.org
X-Pgp-Agent: GPGMail 2.6b2
From: John Payne <john@sackheads.org>
In-Reply-To: <56CDFA68.4030506@gmail.com>
Date: Mon, 18 Jul 2016 07:42:44 -0400
X-Mao-Original-Outgoing-Id: 490534963.965422-b09664e69fb474290981cc5be3cb3bdf
Message-Id: <D099A405-087B-4A01-897D-F49EC8C43D2D@sackheads.org>
References: <CAL0qLwYZPO9L9e7MHA6zP5vcTbQEJmwCSonLdMeQiOw4CUoiFw@mail.gmail.com> <20140718174827.652621ADAF@ld9781.wdf.sap.corp> <6.2.5.6.2.20140719235353.0c50d260@resistor.net> <25621.1405862805@sandelman.ca> <56CDC083.7020001@sandelman.ca> <CAA=duU0HLdE0WRcM3o9SXGuZ2T6E5mha+GjRkyGfPEe+VO=pdg@mail.gmail.com> <87B045CE-2C2F-4528-937E-772B67E26F8C@vigilsec.com> <1301.1456329984@obiwan.sandelman.ca> <56CDFA68.4030506@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/w_0roo6Fx0YgXAC1Ot_xMLHL1fY>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, IETF <ietf@ietf.org>
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: Mon, 18 Jul 2016 11:43:29 -0000

> On Feb 24, 2016, at 1:46 PM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> 
> On 25/02/2016 05:06, Michael Richardson wrote:
>> 
>> Russ Housley <housley@vigilsec.com> wrote:
>>> We are in the process of upgrading mailman. As part of that upgrade
>>> there are new settings. The Secretariat has been discussing the various
>>> choices for those new settings with some of the Tools Team. If there is
>>> anyone in the community that has a lot of experience with mailman
>>> setting, we would like to consult with you.
>> 
>> Good, thank you for this update.
>> 
>> I'd like to ask that we capture the reasons (the thought process) for the
>> settings into at least a wiki page, if not a BCP.
> 
> Yes, and maybe leave a little time for public debate before implementation,
> because a lot of people's working habits may be affected.

Things seem to have been (publicly) silent on the topic of IETF mailing lists and DMARC since feb.  Can we have an update please?

Thanks
John

v2.23.0 | Report a Bug | By Email