Re: Mailing list membership.

Miles Fidelman <mfidelman@meetinghouse.net> Thu, 02 March 2017 01:04 UTC

Return-Path: <mfidelman@meetinghouse.net>
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 93F89129445 for <ietf@ietfa.amsl.com>; Wed, 1 Mar 2017 17:04:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 G0OpGegsk9Jj for <ietf@ietfa.amsl.com>; Wed, 1 Mar 2017 17:04:11 -0800 (PST)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id E58DE129431 for <ietf@ietf.org>; Wed, 1 Mar 2017 17:04:10 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id F04D54F80B9 for <ietf@ietf.org>; Wed, 1 Mar 2017 20:04:09 -0500 (EST)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id hdyzxndJvOUg for <ietf@ietf.org>; Wed, 1 Mar 2017 20:04:08 -0500 (EST)
Received: from Miless-MacBook-Pro.local (ip98-167-249-95.ph.ph.cox.net [98.167.249.95]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 30E434F80B2 for <ietf@ietf.org>; Wed, 1 Mar 2017 20:04:08 -0500 (EST)
Subject: Re: Mailing list membership.
To: ietf@ietf.org
References: <6.2.5.6.2.20170226124145.0b7b38c0@elandnews.com> <20f0d769-1937-3256-e37b-9583399c11d3@riseup.net> <20170227011852.GA5403@mx4.yitter.info> <5850e685-2f97-2bdb-87e2-0c11830e1d1c@riseup.net> <HE1PR04MB14490315646CDD5CC7DC2DBCBD570@HE1PR04MB1449.eurprd04.prod.outlook.com> <ae531393-b622-a8b3-2cdd-65a4e99c6e9f@riseup.net> <HE1PR04MB14490DE8834559F6D9D05F7EBD570@HE1PR04MB1449.eurprd04.prod.outlook.com> <60cc8784-2815-32df-0cae-7adfffd0b549@riseup.net> <20170228051843.wkh5skthuyrs5pwz@thunk.org> <bea06868-c7b9-29ec-4f63-1adcca3b9698@riseup.net> <20170301044937.v3vhw3eqgqkxpoup@thunk.org> <cfb52458-8bb9-58fe-d80a-f1b17a6da6cc@comcast.net> <947BCD81-7F9C-4C2E-ADDE-D68DD2BF513A@gmail.com>
From: Miles Fidelman <mfidelman@meetinghouse.net>
Message-ID: <a43346b6-82ca-ec59-705a-061940299699@meetinghouse.net>
Date: Wed, 01 Mar 2017 18:04:06 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <947BCD81-7F9C-4C2E-ADDE-D68DD2BF513A@gmail.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/eJg39f0ZndgK5vzmyVhLVBZl56E>
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: Thu, 02 Mar 2017 01:04:12 -0000

On 3/1/17 12:14 PM, Bob Hinden wrote:

> Mike,
>
>> On Mar 1, 2017, at 10:55 AM, Michael StJohns <mstjohns@comcast.net> wrote:
>>
>>> Hence mailing list systems that enforce DMARC, or request DMARC
>>> processing, are fundamentally incompatible with mailing lists as
>>> defined by section 3.10.2 of RFC 2821.
>>>
>>> If you want to participate in such mailing list, one of the best ways
>>> is to change to a mailing list system that doesn't do DMARC.
>>>
>>> Best regards,
>>>
>>> 						- Ted
>>>
>> Thanks for the clear description of the problem - I admit that I got a similar one from folks at the Seoul IETF.
>>
>> In the short term, one thing I think would be helpful is to identify for the IETF participants which email providers are known to use DMARC and maybe also a list of providers that are known not to.   Maybe add it to the IETF mailing list page at https://www.ietf.org/list/ with an explanation of what's been happening.
>>
> 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.
>
Yes, but that warning should be on the subscription web page, or the 
list manager should be tuned to make sure that the warning notice 
doesn't get rejected by DMARC!

Miles Fidelman

-- 
In theory, there is no difference between theory and practice.
In practice, there is.  .... Yogi Berra