[Top] [All Lists]

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

2020-03-05 21:28:07
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
To: =?UTF-8?B?bGludXgtdGlwLWNvbW1pdHNAdmdlci5rZXJuZWwub3Jn?
X-Mailer: =?UTF-8?B?dGlwLWdpdC1sb2ctZGFlbW9u?=
Robot-ID: =?UTF-8?B?PHRpcC1ib3QuZ2l0Lmtlcm5lbC5vcmc+?=
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(_at_)zytor(_dot_)com>
To: linux-tip-commits(_at_)vger(_dot_)kernel(_dot_)
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: <>
Robot-unsubscribe: Contact <mailto:hpa(_at_)kernel(_dot_)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... :)

Attachment: pgpdleuu7eDxa.pgp
Description: PGP signature

ietf-smtp mailing list