Re: Mailing list membership.

Michael StJohns <mstjohns@comcast.net> Wed, 01 March 2017 18:55 UTC

Return-Path: <mstjohns@comcast.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 772E712966A for <ietf@ietfa.amsl.com>; Wed, 1 Mar 2017 10:55:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.net
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 YJwiPMn3GYiL for <ietf@ietfa.amsl.com>; Wed, 1 Mar 2017 10:55:58 -0800 (PST)
Received: from resqmta-ch2-07v.sys.comcast.net (resqmta-ch2-07v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:39]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 16C03129663 for <ietf@ietf.org>; Wed, 1 Mar 2017 10:55:58 -0800 (PST)
Received: from resomta-ch2-05v.sys.comcast.net ([69.252.207.101]) by resqmta-ch2-07v.sys.comcast.net with SMTP id j9PXcpaF87NeDj9Ppc6MUx; Wed, 01 Mar 2017 18:55:57 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20161114; t=1488394557; bh=px3XBGK4d/RbqsOu+i2wNadDUay2mH/x9tLLCHJ0/gI=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=mhpkLysgH8Q4x5q4WLY0LX377IvTspXAM7oHW/k/owNUxrTrKC4b+0xYCz3D7js5Z a+6P7kdfTYmzv410gKLqZfwmG+cCWgZqEXJnTSs9oFDYHFR1lHKP3oLksrAKSwVUd5 pLD4nkRRPg/3NcpUfGdYr4cyDIOQKDlsP2iasNKayzGIZ1fF3KrPDATT4qyRGJgnsp X1i2V23oBSpgs6/lOII2/mbya1ELgjD0st7Z7RDdDOw3h7JVJUrVYiV2fE70xvJ84N xpYlKOcbVdipJyFPp4NinhTA4T12zS1r7oewBdPzNx9uTeO5K2dGQstF9lrfzqNG7m RYJQwL0pyJY7w==
Received: from [IPv6:2601:152:4400:9b5f:c8f0:67e5:88b1:2975] ([IPv6:2601:152:4400:9b5f:c8f0:67e5:88b1:2975]) by resomta-ch2-05v.sys.comcast.net with SMTP id j9Poc8G3ge2G0j9PoccRDo; Wed, 01 Mar 2017 18:55:57 +0000
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>
From: Michael StJohns <mstjohns@comcast.net>
Message-ID: <cfb52458-8bb9-58fe-d80a-f1b17a6da6cc@comcast.net>
Date: Wed, 01 Mar 2017 13:55:59 -0500
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <20170301044937.v3vhw3eqgqkxpoup@thunk.org>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
X-CMAE-Envelope: MS4wfAlsjPxsCi/GU92721vASf9KLkcB2QNl7suQ9uFvcuxCY1+AhaLfcz2uXNv0LWExFaKX8Ut2bFs1A9s6Zll+1e5dL2dT5EqCa0hD9Hvm9jT+FmzdbZed avzXVy6BA2c9ksP10sWQlC8wXxJEi5NdqvQMblefBuL6EdIRGdmZsKVlAEeenckDgwx+sxsj1IRRQA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/CRAXQMYEMuCQF-ffFEpXOot9VZ4>
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: Wed, 01 Mar 2017 18:55:59 -0000

Question below

On 2/28/2017 11:49 PM, Theodore Ts'o wrote:
> On Tue, Feb 28, 2017 at 05:29:24PM -0300, willi uebelherr wrote:
>> related to the problem, what Khaled explained, what is your proposal?
>>
>> What are your "compatible with internet mailing lists" mail systems?
> RFC 2821, Simple Mail Transfer Protocol, section 3.10.2
>
>     "To expand a list, the recipient mailer replaces the
>     pseudo-mailbox address in the envelope with all of the expanded
>     addresses.  The return address in the envelope is changed so that all
>     error messages generated by the final deliveries will be returned to
>     a list administrator, not to the message originator, who generally
>     has no control over the contents of the list and will typically find
>     error messages annoying."
>
> This is the SMTP Envelope From field.  The FROM field is not changed,
> but the SMTP return address is changed, so that bounces go to the
> mailing list administrator as opposed to the person who sends mail to
> the mailing list.
>
> Unfortunately, if you are using a system whose domain requests that
> all recipients enforce DMARC alignment, this specifically instructs
> recipients to bounce mail if the SMTP Envelope return address doesn't
> match the FROM field in the header.  This means that they won't see
> mailing list mail as defined by the IETF Standards Track RFC 2821,
> which specifically says that is acceptable (and in fact a good thing)
> to change the SMTP envelope return address so that bounces (caused by
> people changing where they work, etc.) go to an administrator who can
> deal with them.  But if the mailing list administrators gets too may
> bounces, and it's because the sending domain is requesting that mail
> be bounced, the only thing they can do is to unsubscribe the sender or
> the recipient.
>
> 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.


Mike