IETF Logo Mail Archive

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

John Levine <johnl@taugh.com> Thu, 05 March 2020 04:34 UTC

Return-Path: <johnl@iecc.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 F0E813A0B8E for <ietf-smtp@ietfa.amsl.com>; Wed, 4 Mar 2020 20:34:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.85
X-Spam-Level:
X-Spam-Status: No, score=-1.85 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, HEADER_FROM_DIFFERENT_DOMAINS=0.25, 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=qjHNUEBB; dkim=pass (1536-bit key) header.d=taugh.com header.b=bo4FnGH+
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 L0YW-Sp9aHxR for <ietf-smtp@ietfa.amsl.com>; Wed, 4 Mar 2020 20:34:16 -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 94E0E3A0B91 for <ietf-smtp@ietf.org>; Wed, 4 Mar 2020 20:34:16 -0800 (PST)
Received: (qmail 42437 invoked from network); 5 Mar 2020 04:34:14 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:mime-version:content-type:content-transfer-encoding; s=a5c3.5e608146.k2003; bh=0vSWI1JXfHtwZIAUiGiiNQrOZJ+I/Ff409fEv1cs/rY=; b=qjHNUEBBIgKdMLXAn9THuGpU+F10DQ+XV8a+IJVF1GHQlqDSi6S16i7FhGQ/W3ifOT+n8F4LvUWb4BzEI9fJI7d1MLGChH+rGjnOlWHDox12TMATC5nHsGrJ1SQCSnDvIsfoikKhch6GD9eXBhbaibG8UjOSM1Op70TtwuS4pSytagaRshzK0nha5Tv6KNi2ZXIB3Zm6CBeoCJ41Bb0omjn/poFNd6QpzRI1MeylLGAyRgmG+If5xFS6MaBPi3bV
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:mime-version:content-type:content-transfer-encoding; s=a5c3.5e608146.k2003; bh=0vSWI1JXfHtwZIAUiGiiNQrOZJ+I/Ff409fEv1cs/rY=; b=bo4FnGH+TuxKf9pNU0JDA05JYPF+A9GpTCgYdxD3gdaAatHlrmfSLthySujt1NiA+99EBBHWCStq5hkKxIY5MIPZR1nPJ+QKy6nTRJNDABpJjf04fOV+dAJmoUJ6Odj646XK86dx/OeqYzUKmugd3kngobxNchdCXPQY3+6Ep5ltjmTF8VeWHTPC0l/BF2xkif+ep/5yN1A0ExjDPd3Xgkq6P94SsIAT/xD6bOv847td5skK/v8N7iYLCiSymacm
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTP via TCP6; 05 Mar 2020 04:34:14 -0000
Received: by ary.qy (Postfix, from userid 501) id 0E7C515740C2; Wed, 4 Mar 2020 23:34:13 -0500 (EST)
Date: Wed, 04 Mar 2020 23:34:13 -0500
Message-Id: <20200305043414.0E7C515740C2@ary.qy>
From: John Levine <johnl@taugh.com>
To: ietf-smtp@ietf.org
Organization: Taughannock Networks
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/BDUDorKA6XCuMP8MlySlzPGXejo>
Subject: [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: Thu, 05 Mar 2020 04:34:21 -0000

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.

Message-ID: =?utf-8?q?=3CBN7PR11MB25474DF04998FF3AA9E0B80BC9E40=40BN7PR11MB2?= =?utf-8?q?547=2Enamprd11=2Eprod=2Eoutlook=2Ecom=3E?=

R's,
John

PS: Same question about References with mime-encoded text.

* - actually I copy the messages to my local news server so I can use
threading and killfiles.  The copy program was having trouble with
the message-ids, which NNTP needs to do duplicate detection.

v2.23.0 | Report a Bug | By Email