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

John R Levine <johnl@taugh.com> Fri, 06 March 2020 04:40 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 0E82C3A1359 for <ietf-smtp@ietfa.amsl.com>; Thu, 5 Mar 2020 20:40:06 -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=RhP/Uu72; dkim=pass (1536-bit key) header.d=taugh.com header.b=fwm0HyEQ
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 Jq75GZIZ-GJt for <ietf-smtp@ietfa.amsl.com>; Thu, 5 Mar 2020 20:40:04 -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 E15843A1358 for <ietf-smtp@ietf.org>; Thu, 5 Mar 2020 20:40:03 -0800 (PST)
Received: (qmail 26552 invoked from network); 6 Mar 2020 04:40:02 -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=67b5.5e61d422.k2003; i=johnl-iecc.com@submit.iecc.com; =?utf-8?q?bh=3DwVXmOz5QOq9n+BsEzh34mcoAocA3lb8Rz1NGqUcCscE=3D=3B_b=3DRhP/Uu?= =?utf-8?q?72cwRZsIOd3uqfMXCsrzHbJTVZZ+RDl+dz+TELnMJnVE+cwb+8d2aptWk7CTAQVvW?= =?utf-8?q?209buw0ssH5sUKo1yWKNAf87pCBtO95QWnIOWmlLRt3qeI9CPGfSbn03V3VWoTyPk?= =?utf-8?q?pEpXbSdP8ks+/5c0Tdwt0vD9gS/MgJvjOh9dT/rCUrYwrpwUT82tocyDbI8qe9lo9?= =?utf-8?q?ffC5YdsI4mrQvYUQTeF1DFOLd6A/nl9mFiYSOvp+xQ62Mwx/PdoWMb1?=
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=67b5.5e61d422.k2003; olt=johnl-iecc.com@submit.iecc.com; =?utf-8?q?bh=3DwVXmOz5QOq9n+BsEzh34mcoAocA3lb8Rz1NGqUcCscE=3D=3B_b=3Dfwm0Hy?= =?utf-8?q?EQdBXgaA721q7S/pp0z473VV+vfdtJWM1BG3krCPWLl+nhAJ5Xb0DcA0W7yS0G8Cb?= =?utf-8?q?SGVF8km2iBOSknYa7XvBe9eUIo+fj++mdr5jcw9adjLz1dz1I3hWEElYQ9vQcRZh4?= =?utf-8?q?tazwcN9CANW/uQ0wSIrfvnZQ4bqZ/HTyCs5Rfe448V3hH062JmJ9Mh5DQWUhW6hCf?= =?utf-8?q?rbnqj31FS8c5TxQr+Svz8bMYnVRxgnKnIgwXP5jNnTSuM0U7TA0aBOK?=
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 04:40:01 -0000
Date: 5 Mar 2020 23:40:01 -0500
Message-ID: <alpine.OSX.2.22.407.2003052339010.19976@ary.qy>
From: "John R Levine" <johnl@taugh.com>
To: "Mark Andrews" <marka@isc.org>
Cc: ietf-smtp@ietf.org
In-Reply-To: <9DF11014-4C79-49DE-B17E-12B87F2FF17C@isc.org>
References: <20200305043414.0E7C515740C2@ary.qy> <87055.1583465260@turing-police> <9DF11014-4C79-49DE-B17E-12B87F2FF17C@isc.org>
User-Agent: Alpine 2.22 (OSX 407 2020-02-09)
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="0-617178521-1583469601=:19976"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/GSEJhxVwENoMGzPm2I6tKfx_dDU>
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 04:40:06 -0000

On Fri, 6 Mar 2020, Mark Andrews wrote:
> Conversion of all ASCII headers to utf-8 mime encoded should be banned. Apart
> from testing encoding/decoding it serves no useful purpose and if you want
> to perform such testing you can always add a non ASCII character.  MUA’s that
> do this are deliberately breaking interoperability with old MUAs.

The spec is pretty clear where you can have MIME entities and where you 
can't.  You can't have them in Message-ID's, References, or the actual 
address in To, From, Cc, etc.

R's,
John

>
> Mark
>
>> On 6 Mar 2020, at 14:27, Valdis Klētnieks <valdis.kletnieks@vt.edu> wrote:
>>
>> On 04 Mar 2020 23:34:13 -0500, "John Levine" said:
>>> I read IETF mailing lists on the IETF's IMAP server* and of late I've been
>>> seeing some awfully funky stuff.
>>>
>>> This is an actual Message-ID header in one of the messages in dnsop.
>>> Is that valid?  Even though the MIME decodes to a an ASCII message ID
>>> in the <string@domain> format, I think the answer is no.  That's not
>>> what RFC 5322 sec 3.6 allows.
>>
>> I'll see your Message-ID, and raise you a... not even sure *what* to call it. :)
>>
>>> From my collection of emails that give exmh indigestion:
>>
>> % grep UTF-8 183
>> From: =?UTF-8?B?dGlwLWJvdCBmb3IgRGF2aWQgQnJvd24gPHRpcGJvdEB6eXRvci5jb20+?=@zytor.com
>> To: =?UTF-8?B?bGludXgtdGlwLWNvbW1pdHNAdmdlci5rZXJuZWwub3Jn?=@zytor.com
>> Subject: =?UTF-8?B?W3RpcDptbS9yZWFkb25seV0gQVJNL3Zkc286IE1hcmsgdGhlIHZEU08gY29kZSA=?=  =?UTF-8?B?cmVhZC1vbmx5IGFmdGVyIGluaXQ=?=
>> Git-Commit-ID: =?UTF-8?B?MTFiZjliODY1ODk4OTYxY2VlNjBhNDFjNDgzYzlmMjdlYzc2ZTEyZQ==?=
>> X-Mailer: =?UTF-8?B?dGlwLWdpdC1sb2ctZGFlbW9u?=
>> Robot-ID: =?UTF-8?B?PHRpcC1ib3QuZ2l0Lmtlcm5lbC5vcmc+?=
>> Robot-Unsubscribe: =?UTF-8?B?Q29udGFjdCA8bWFpbHRvOmhwYUBrZXJuZWwub3JnPiB0byBnZXQgYmxhY2tsaXM=?=  =?UTF-8?B?dGVkIGZyb20gdGhlc2UgZW1haWxz?=
>> MIME-Version: =?UTF-8?B?MS4w?=
>> Content-Transfer-Encoding: =?UTF-8?B?OGJpdA==?=
>> Content-Type: =?UTF-8?B?dGV4dC9wbGFpbjsgY2hhcnNldD1VVEYtOA==?=
>> Content-Disposition: =?UTF-8?B?aW5saW5l?=
>>
>> Amazingly enough, this managed to collect 10 Received: headers, land in my
>> mailbox, and exmh *mostly* figured it out:
>>
>> From: tip-bot for David Brown <tipbot@zytor.com>@zytor.com
>> To: linux-tip-commits@vger.kernel.org@zytor.com
>> Subject: [tip:mm/readonly] ARM/vdso: Mark the vDSO code   read-only after init
>> Git-commit-id: 11bf9b865898961cee60a41c483c9f27ec76e12e
>> X-mailer: tip-git-log-daemon
>> Robot-id: <tip-bot.git.kernel.org>
>> Robot-unsubscribe: Contact <mailto:hpa@kernel.org> to get blacklis  ted from these emails
>> Mime-version: 1.0
>> Content-transfer-encoding: 8bit
>> Content-type: text/plain; charset=UTF-8
>> Content-disposition: inline
>>
>> But then finally gave up because it tried to use the undecoded content-type,
>> gave up, and tossed up a "save/print/don't decode MIME" dialog.
>>
>> And yes, tip-bot got fixed quite quickly thereafter... :)
>> _______________________________________________
>> ietf-smtp mailing list
>> ietf-smtp@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf-smtp
>
>

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