Re: [ietf-smtp] Curious, with this now being associated to emailcore, should list name change?

John C Klensin <john-ietf@jck.com> Sun, 19 July 2020 00:58 UTC

Return-Path: <john-ietf@jck.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 DC7113A0EE4 for <ietf-smtp@ietfa.amsl.com>; Sat, 18 Jul 2020 17:58:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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 krXwwKNWlNoB for <ietf-smtp@ietfa.amsl.com>; Sat, 18 Jul 2020 17:58:00 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C3EF63A0EE2 for <ietf-smtp@ietf.org>; Sat, 18 Jul 2020 17:58:00 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1jwxeR-00082t-0k; Sat, 18 Jul 2020 20:57:59 -0400
Date: Sat, 18 Jul 2020 20:57:53 -0400
From: John C Klensin <john-ietf@jck.com>
To: E Sam <winshell64@gmail.com>, ietf-smtp@ietf.org
Message-ID: <5C6196E28FCDC4A312E73A00@PSB>
In-Reply-To: <CAKFo7wmsm+1ck5G7Sj-NpnyXgeHd14cxGQ6K9KFeVG0_CTM1sw@mail.gmail.com>
References: <81c2a19c-f19e-b495-3441-22c2a112037c@linuxmagic.com> <52D9A14B4CDD14BB4C97C355@PSB> <CAKFo7w=9_eZda47ZMUv_NE9iN1FEnGM7m3nUFy3_Wq4se+W8XQ@mail.gmail.com> <DE8B2C33275660E19FFA513C@PSB> <CAKFo7wmsm+1ck5G7Sj-NpnyXgeHd14cxGQ6K9KFeVG0_CTM1sw@mail.gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/rwO8gteYc48GAexD7JSuBDo0zB0>
Subject: Re: [ietf-smtp] Curious, with this now being associated to emailcore, should list name change?
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: Sun, 19 Jul 2020 00:58:02 -0000


--On Saturday, July 18, 2020 18:56 -0400 E Sam
<winshell64@gmail.com> wrote:

> I think the max size of the header name does need to be
> addressed in RFC 5322. Seeing how email and Usenet can
> sometimes be the "wild west" I have seen really long headers
> and developing mail software the question of header max limits
> have also come into my mind.

Out of curiosity and just to be precise, are you talking about
the header field name or the field value?

> The other issues on the list are important too but this one is
> one that I have personally dealt my hands on.

I trust Pete and the co-chairs will take note.

> I look forward to seeing what comes out of the BOF.

Time zones, etc., permitting, please try to participate.  Much
of the BOF is precisely about deciding what is in or out of
scope.

best,
   john