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

Alexey Melnikov <alexey.melnikov@isode.com> Wed, 22 July 2020 12:28 UTC

Return-Path: <alexey.melnikov@isode.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 F0CC13A0AE6 for <ietf-smtp@ietfa.amsl.com>; Wed, 22 Jul 2020 05:28:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isode.com
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 19FBq6QLjIrC for <ietf-smtp@ietfa.amsl.com>; Wed, 22 Jul 2020 05:28:37 -0700 (PDT)
Received: from waldorf.isode.com (waldorf.isode.com [62.232.206.188]) by ietfa.amsl.com (Postfix) with ESMTP id A2A9C3A0AE1 for <ietf-smtp@ietf.org>; Wed, 22 Jul 2020 05:28:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1595420916; d=isode.com; s=june2016; i=@isode.com; bh=frHhorm+I6aV0RgEFnfIs3WtSum+y2KnGULkyo0yq58=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=lXzGab7XWMliwHSBwCvJJrDleEh68U4V5odC3iOZrgiX8iIlXCYfTWbmz/dQuX84ZIfRA2 PiQA4AycVxdpeSaSlz7sDSANLaXuzPGlg/PJlSKBaBHsN9wvsuCToS+1unOTwUdTdAQSID wKbXpgSvUHVRaYqiA4t6Pxw+I5x8fSI=;
Received: from [172.27.248.213] (connect.isode.net [172.20.0.72]) by waldorf.isode.com (submission channel) via TCP with ESMTPSA id <Xxgw8wAkBjFz@waldorf.isode.com>; Wed, 22 Jul 2020 13:28:36 +0100
To: Keith Moore <moore@network-heretics.com>, John C Klensin <john-ietf@jck.com>
References: <3460DCD7D42390BD22FECF60@JcK-HP5.jck.com> <25eb1142-88ed-3502-0db9-17763dffa96e@network-heretics.com>
From: Alexey Melnikov <alexey.melnikov@isode.com>
Cc: ietf-smtp@ietf.org
Message-ID: <886a74c3-0d89-60df-2b11-049dec95d164@isode.com>
Date: Wed, 22 Jul 2020 13:28:20 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.9.0
In-Reply-To: <25eb1142-88ed-3502-0db9-17763dffa96e@network-heretics.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------AEF250BA7FAC0EF1FDA8C7B3"
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/vcY71mySAa5pgrjJ-97fouCWwWE>
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: Wed, 22 Jul 2020 12:28:39 -0000

On 22/07/2020 07:04, Keith Moore wrote:

> On 7/22/20 1:49 AM, John C Klensin wrote:
>
>>> I love the format's extensibility but I suspect there's a
>>> point of diminishing returns.   The message header has
>>> become a garbage dumping ground, and it might need some
>>> cleaning up.
>> Agreed.  But also agree with Dave that it is difficult to
>> imagine how cleaning up such a dump (even if there were
>> consensus on that characterization) could be within scope for
>> emailcore.   It probably is in scope for this list [1] but I
>> hope we
>> don't need to separate emailcore to a separate list in order to
>> get anything done there.   ...Another decision I hope we can
>> defer until after the BOF.
>
> I will certainly agree that there is no immediately obvious fix to the 
> header garbage dump problem.
>
> As for the list, if emailcore goes on for more than a few weeks, I 
> think it could be problematic to devote the ietf-smtp list exclusively 
> to that narrow set of topics.  ietf-smtp has served since the early 
> 1990s as a general discussion on SMTP-related topics with even that 
> scope interpreted somewhat widely.   There's a lot of inertia around 
> treating the list that way, and it seems like conflicts over the scope 
> of the discussion are inevitable if the same list tries to serve both 
> purposes.
>
I am open to suggestions whether or not EMAILCORE should have its own 
mailing list. But I think until the BOF is over, we can use this 
(ietf-smtp@ietf.org) mailing list, as most of the people who care are 
already subscribed to it.
>
> More subtly, some solutions are not within the scope of emailcore even 
> if the topic or problem is.
>
> So my recommendation is to use a separate list for emailcore.
>
> For what it's worth, when I was musing about the harm done by email 
> header pollution, I didn't expect that the solution was likely to fit 
> within emailcore's scope.
>
> Keith
>
>