Re: Enabling DMARC workaround code for all IETF/IRTF mailing lists
John C Klensin <john-ietf@jck.com> Fri, 11 May 2018 18:05 UTC
Return-Path: <john-ietf@jck.com>
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 3102A126E01 for <ietf@ietfa.amsl.com>; Fri, 11 May 2018 11:05:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 SdIqTQWquPD3 for <ietf@ietfa.amsl.com>; Fri, 11 May 2018 11:05:05 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BC825126C2F for <ietf@ietf.org>; Fri, 11 May 2018 11:05:05 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1fHCPg-000CK3-MO; Fri, 11 May 2018 14:05:04 -0400
Date: Fri, 11 May 2018 14:04:57 -0400
From: John C Klensin <john-ietf@jck.com>
To: Alexey Melnikov <aamelnikov@fastmail.fm>
cc: ietf@ietf.org
Subject: Re: Enabling DMARC workaround code for all IETF/IRTF mailing lists
Message-ID: <8CC6D9B2CECAC709CCB8FA5E@PSB>
In-Reply-To: <739143A6-90EB-4F26-8F54-B281DA2FB0E4@fastmail.fm>
References: <919855CA-9F77-420A-8B8F-79174CD2FC19@fastmail.fm> <61B1EDB45FC4FF33154B13B0@PSB> <739143A6-90EB-4F26-8F54-B281DA2FB0E4@fastmail.fm>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/7Bq0LwnLrE7argP8QYstb0uE5Jw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: Fri, 11 May 2018 18:05:08 -0000
--On Friday, May 11, 2018 20:17 +0300 Alexey Melnikov <aamelnikov@fastmail.fm> wrote: > Deploying EAI for IETF mailing lists would be a big > undertaking in itself. We can cross this bridge when we need > to cross it. My only concern is that, unless the IETF is going to consider making SMTPUTF8 "not recommended", we do nothing that would either make deploying it harder or encourage non-conforming hacks that would have the same effect. Neither of those require deploying it or deciding it would be a good idea for IETF mailing lists (personally, I think it would not be), only that we think about the possibility. From that perspective, "cross that bridge when we come to it" sounds a bit like "put heads in sand". >> With the understanding that I'm holding my nose while saying >> this (because I have been happy to see the convention fade >> from use), we already have a widely-supported and recognized >> convention for this type of encoding and I wonder why those >> who have been involved with this effort rejected it. That >> would be to use >> alexey%example.com@dmarc.ietf.org > > The short answer is that Henrik tries to use % and found that > various software (including some non IETF mailing lists, if I > remember correctly) was buggy and assigned some special > meaning to % that made it unsuitable for our purposes. Very good. If the possibility was considered and caused its own set of problems, then I'm happy avoiding it. I believe it would be helpful to document what issues have been found in some way, if only because that information would be helpful if we ever try to advance 5321/5322 on the standards track. thanks and best regards, john
- Re: Enabling DMARC workaround code for all IETF/I… Andrew G. Malis
- Re: Enabling DMARC workaround code for all IETF/I… Russ Housley
- Re: Enabling DMARC workaround code for all IETF/I… Andrew G. Malis
- Enabling DMARC workaround code for all IETF/IRTF … Alexey Melnikov
- Re: Enabling DMARC workaround code for all IETF/I… Andrew G. Malis
- Re: Enabling DMARC workaround code for all IETF/I… John C Klensin
- RE: Enabling DMARC workaround code for all IETF/I… MH Michael Hammer (5304)
- RE: Enabling DMARC workaround code for all IETF/I… John C Klensin
- Re: Enabling DMARC workaround code for all IETF/I… Alexey Melnikov
- Re: Enabling DMARC workaround code for all IETF/I… Ted Lemon
- Re: Enabling DMARC workaround code for all IETF/I… Andrew G. Malis
- Re: Enabling DMARC workaround code for all IETF/I… John C Klensin
- Re: Enabling DMARC workaround code for all IETF/I… Spencer Dawkins at IETF
- Re: Enabling DMARC workaround code for all IETF/I… John C Klensin
- Re: Enabling DMARC workaround code for all IETF/I… Viktor Dukhovni
- Re: Enabling DMARC workaround code for all IETF/I… Spencer Dawkins at IETF
- Re: Enabling DMARC workaround code for all IETF/I… John Levine
- Re: Enabling DMARC workaround code for all IETF/I… John C Klensin
- Re: Enabling DMARC workaround code for all IETF/I… Viktor Dukhovni
- Re: Enabling DMARC workaround code for all IETF/I… John Levine
- Re: Enabling DMARC workaround code for all IETF/I… Viktor Dukhovni
- Re: Enabling DMARC workaround code for all IETF/I… Hector Santos
- Integrity of mail systems (was Re: Enabling DMARC… Andrew Sullivan
- Re: Enabling DMARC workaround code for all IETF/I… Alessandro Vesely
- Re: Integrity of mail systems (was Re: Enabling D… John C Klensin
- Re: Integrity of mail systems (was Re: Enabling D… Michael Richardson
- Re: Integrity of mail systems (was Re: Enabling D… Phillip Hallam-Baker
- Re: Enabling DMARC workaround code for all IETF/I… Hector Santos
- Re: Enabling DMARC workaround code for all IETF/I… Brandon Long
- Re: Enabling DMARC workaround code for all IETF/I… Brian E Carpenter
- Re: Enabling DMARC workaround code for all IETF/I… Glen