From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <947BCD81-7F9C-4C2E-ADDE-D68DD2BF513A@gmail.com>
Content-Type: multipart/signed;
 boundary="Apple-Mail=_508CEBD7-F872-4EE1-B90B-1E4732862F6E";
 protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Mailing list membership.
Date: Wed, 1 Mar 2017 11:14:05 -0800
In-Reply-To: <cfb52458-8bb9-58fe-d80a-f1b17a6da6cc@comcast.net>
To: Michael StJohns <mstjohns@comcast.net>
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>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/sPXIqTQSPA4WHV_Eu0rov5sOb-k>
Cc: Bob Hinden <bob.hinden@gmail.com>, IETF <ietf@ietf.org>
Precedence: list


--Apple-Mail=_508CEBD7-F872-4EE1-B90B-1E4732862F6E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Mike,

> On Mar 1, 2017, at 10:55 AM, Michael StJohns <mstjohns@comcast.net> =
wrote:
>=20
>>=20
>> 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.
>>=20
>> 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.
>>=20
>> Best regards,
>>=20
>> 						- Ted
>>=20
>=20
> Thanks for the clear description of the problem - I admit that I got a =
similar one from folks at the Seoul IETF.
>=20
> 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.
>=20

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.

Bob



--Apple-Mail=_508CEBD7-F872-4EE1-B90B-1E4732862F6E
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJYtx1+AAoJEK7rdBF357uowEcIAKe6aHjpd8pwEMPpDkLl3wHd
HixrFRjmzP0z8UcSj1jN2/A3gUh+4KwkGE87rO2Je3Gg0MqEdatV6x6WsJMcCiEB
sy1wWVOMCxXzqonBkdDYBYkzbo/Xld3ApiVxSjo3dJXTfIbARSOnb6KQhowA/bfR
nIVBl9wqpnVKgA31kISmeEIPXjgv9Bqo5OmUAb6R5DlCi13mXi7BoNznte0yNEQF
7wY2/3Oz4qwXfN/gmnmUY1nxLkvXOKlJY7Z+KbUOyH4Pvg6Qtet/zlkf/1Tb0PuC
WzMrGZjntzpBWXvfDaDOJfRuFOfiEESzjQTapQl/8WnoxiVCIkpRTV00vEKDRmM=
=moQp
-----END PGP SIGNATURE-----

--Apple-Mail=_508CEBD7-F872-4EE1-B90B-1E4732862F6E--