Re: [ietf-smtp] Is this a valid Message-ID header ?

John R Levine <johnl@taugh.com> Fri, 06 March 2020 16:34 UTC

Return-Path: <johnl@taugh.com>
X-Original-To: ietf-smtp@ietfa.amsl.com
Delivered-To: ietf-smtp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D6A33A0AAE for <ietf-smtp@ietfa.amsl.com>; Fri, 6 Mar 2020 08:34:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=JwbiuMgS; dkim=pass (1536-bit key) header.d=taugh.com header.b=kJzLzH55
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 GCtLtdhikAJW for <ietf-smtp@ietfa.amsl.com>; Fri, 6 Mar 2020 08:34:52 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 6F8D73A0AB5 for <ietf-smtp@ietf.org>; Fri, 6 Mar 2020 08:34:52 -0800 (PST)
Received: (qmail 28336 invoked from network); 6 Mar 2020 16:34:50 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; =?utf-8?q?h=3Ddate?= =?utf-8?q?=3Amessage-id=3Afrom=3Ato=3Acc=3Asubject=3Ain-reply-to=3Areferenc?= =?utf-8?q?es=3Amime-version=3Acontent-type=3Auser-agent=3B?= s=6eaa.5e627baa.k2003; i=johnl-iecc.com@submit.iecc.com; =?utf-8?q?bh=3DADIaJYPMQdfwwKyj0VOOz80glK+cAXmmO3wcUPA5h2Q=3D=3B_b=3DJwbiuM?= =?utf-8?q?gS4GHoE9mEU31BX1SGxECM0/W8Skx+NAvc3/9vHnc4RRCEJHY09Hj+51lntrz/Wud?= =?utf-8?q?9Uc2BGbwpsNDna+sC07fjqo/Pd+JXiisbbx3Ishj8Wml5a+8x0uBBATzzeuklkIre?= =?utf-8?q?2H0fDixL5hjxt6yNn3iLitJm+KA018+gpYYcsRvuHWSjrag8AzG/DTo5b2XSYBITM?= =?utf-8?q?4ar+mzaqMjesEeDOuHlXIMxfUnVb5eCCDk5XftBF80CHy3XPYcyof7/?=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; =?utf-8?q?h=3Ddate?= =?utf-8?q?=3Amessage-id=3Afrom=3Ato=3Acc=3Asubject=3Ain-reply-to=3Areferenc?= =?utf-8?q?es=3Amime-version=3Acontent-type=3Auser-agent=3B?= s=6eaa.5e627baa.k2003; olt=johnl-iecc.com@submit.iecc.com; =?utf-8?q?bh=3DADIaJYPMQdfwwKyj0VOOz80glK+cAXmmO3wcUPA5h2Q=3D=3B_b=3DkJzLzH?= =?utf-8?q?55mIOHZiEztwuoK3jNk6rlOAS5supsPoz5BODm+Wh/aCkFTGhoYs0UhQYw+NPMUIK?= =?utf-8?q?f3kxglo/vQUmrSpQmG5oEwyhx3qq1eoWNuqkBo2WIWABVHkMo3OSSJ3WGZCyDgee2?= =?utf-8?q?K9Nt7Z1PATbs9OQx34YQghjX73QfNsqKhibj8/lzsEw6AXkghQN4dTZ4Od/jLc6kA?= =?utf-8?q?VzFx6JCCR92AJZ/buAMy9CbJ6jia2YLvBvZm744imesr2wWKZmOXxaY?=
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPSA (TLS1.3 ECDHE-RSA AES-256-GCM AEAD, johnl@iecc.com) via TCP6; 06 Mar 2020 16:34:50 -0000
Date: 6 Mar 2020 11:34:50 -0500
Message-ID: <alpine.OSX.2.22.407.2003061129530.22046@ary.qy>
From: "John R Levine" <johnl@taugh.com>
To: "John C Klensin" <john-ietf@jck.com>
Cc: ietf-smtp@ietf.org
In-Reply-To: <961C7C4EA24A110554D88BFA@PSB>
References: <20200305043414.0E7C515740C2@ary.qy> <87055.1583465260@turing-police> <9DF11014-4C79-49DE-B17E-12B87F2FF17C@isc.org> <alpine.OSX.2.22.407.2003052339010.19976@ary.qy> <961C7C4EA24A110554D88BFA@PSB>
User-Agent: Alpine 2.22 (OSX 407 2020-02-09)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/s6u7_d80xSGsd39ZGhdJuiqSp8I>
Subject: Re: [ietf-smtp] Is this a valid Message-ID header ?
X-BeenThere: ietf-smtp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion of issues related to Simple Mail Transfer Protocol \(SMTP\) \[RFC 821, RFC 2821, RFC 5321\]" <ietf-smtp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-smtp>, <mailto:ietf-smtp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-smtp/>
List-Post: <mailto:ietf-smtp@ietf.org>
List-Help: <mailto:ietf-smtp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-smtp>, <mailto:ietf-smtp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Mar 2020 16:35:02 -0000

On Fri, 6 Mar 2020, John C Klensin wrote:
> In the interest of clarity, what you are referring to as "MIME
> entities" are encoded words as specified in RFC 2231.  Right?

Right.

> And because encoded words are not permitted in Message-IDs or
> the other fields you mention, those fields must conform to the
> specified syntax without decoding.   If they don't, it is pretty
> much up to the receiving system what to do about it. ...

That was my understanding, too.  I'm finding these MIME message-ID's in 
the IETF's IMAP server, so now I'm wondering if they were in the original 
message.  Here's one that showed up today.  I think they're all from 
Microsoft.

https://mailarchive.ietf.org/arch/msg/last-call/xTEWTOyy4HOX-wyvFVaOicn2P-I/#

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly