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

Valdis Kl ē tnieks <valdis.kletnieks@vt.edu> Fri, 06 March 2020 04:47 UTC

Return-Path: <valdis@vt.edu>
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 69D553A13B1 for <ietf-smtp@ietfa.amsl.com>; Thu, 5 Mar 2020 20:47:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, PP_MIME_FAKE_ASCII_TEXT=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] 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 Dp483ertXR_n for <ietf-smtp@ietfa.amsl.com>; Thu, 5 Mar 2020 20:47:02 -0800 (PST)
Received: from omr2.cc.vt.edu (omr2.cc.ipv6.vt.edu [IPv6:2607:b400:92:8400:0:33:fb76:806e]) (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 0049B3A13A4 for <ietf-smtp@ietf.org>; Thu, 5 Mar 2020 20:47:01 -0800 (PST)
Received: from mr5.cc.vt.edu (smtp.ipv6.vt.edu [IPv6:2607:b400:92:9:0:9d:8fcb:4116]) by omr2.cc.vt.edu (8.14.4/8.14.4) with ESMTP id 0264l1XH010555 for <ietf-smtp@ietf.org>; Thu, 5 Mar 2020 23:47:01 -0500
Received: from mail-qv1-f71.google.com (mail-qv1-f71.google.com [209.85.219.71]) by mr5.cc.vt.edu (8.14.7/8.14.7) with ESMTP id 0264kuU5028974 for <ietf-smtp@ietf.org>; Thu, 5 Mar 2020 23:47:01 -0500
Received: by mail-qv1-f71.google.com with SMTP id r16so637516qvp.13 for <ietf-smtp@ietf.org>; Thu, 05 Mar 2020 20:47:01 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:from:to:cc:subject:in-reply-to:references :mime-version:content-transfer-encoding:date:message-id; bh=VVJ1yhlbLTJJi6EQ2lcW8kwZh8uWOxghot986y8hEOY=; b=l3zwVQ39CaIUMSHVcA2gkKbOfgv+IrTDn6uBPJwh7JDF3QPZL953gkcxiBOeWjRAj4 CvOTFSHjzqaQxQKnrxHBS6iZiDZTwLuVAD71B+6+V+dmPdnNzZt7fX3ZGzKqRIqwQhDD aFUMOExHY4KTxU/bl4R0Rl+BFhW+TBInxZkFbggGU8Le4FU+cCdlTtrUir7SaSg1hiJX vRhalRYCMXKtJBFpfnDwrsVnjF2cqyAr66wJ0f/61hNhpVBW0G0zwouH5mdGpGH1Qk/T F6UiWi4AEkSpSQjV1qBU0FL5VCxeoanNj+D/xmLe6M1l/k7GF5JfN43Lg18AuV2r1NIZ 9L+g==
X-Gm-Message-State: ANhLgQ0chSKcml6jR0nPMM05e9NolArfP48EMdOozYms1KeO3fACjyCx 14ghLWmqqgM6j9zr7ISQZm3i6pJWy0tHTxN04gzg53r/9qeeOhiBziKmCtWkl7WU9a1RuDWnboD W3VDU7TSfZpt7FJUgdY56kQ==
X-Received: by 2002:a05:6214:8b:: with SMTP id n11mr1434882qvr.72.1583470015294; Thu, 05 Mar 2020 20:46:55 -0800 (PST)
X-Google-Smtp-Source: =?utf-8?q?ADFU+vvxW4ZgkV4Zn1rOTuDJKVglR02j7NmT+fy6C9RD?= =?utf-8?q?991RVUcO9sdSfYXBAjHF8qM6ghpubGNNIA=3D=3D?=
X-Received: by 2002:a05:6214:8b:: with SMTP id n11mr1434874qvr.72.1583470014950; Thu, 05 Mar 2020 20:46:54 -0800 (PST)
Received: from turing-police ([2601:5c0:c001:c9e1::359]) by smtp.gmail.com with ESMTPSA id 69sm1949306qki.131.2020.03.05.20.46.53 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 05 Mar 2020 20:46:53 -0800 (PST)
Sender: Valdis Kletnieks <valdis@vt.edu>
From: "Valdis Kl=?utf-8?Q?=c4=93?=tnieks" <valdis.kletnieks@vt.edu>
X-Google-Original-From: "Valdis Kl=?utf-8?Q?=c4=93?=tnieks" <Valdis.Kletnieks@vt.edu>
X-Mailer: exmh version 2.9.0 11/07/2018 with nmh-1.7+dev
To: Mark Andrews <marka@isc.org>
Cc: John Levine <johnl@taugh.com>, 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>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_1583470012_96129P"; micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Thu, 05 Mar 2020 23:46:52 -0500
Message-ID: <96497.1583470012@turing-police>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/TqAYBd_S7zS8rbqWVurPLHtSDOM>
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:47:10 -0000

On Fri, 06 Mar 2020 14:36:18 +1100, Mark Andrews said:
> 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.

You apparently missed the part where the broken bot was quickly fixed...

(And now that I think about it, exmh was actually meta-buggy in that it
accepted a utf-8 encoded Mime-version: header rather than treat it as
a flat non-Mime mail...)