Re: [ietf-smtp] [Emailcore] Document updates and interactions with the ietf-smtp mailing list
Alexey Melnikov <aamelnikov@fastmail.fm> Wed, 30 September 2020 14:11 UTC
Return-Path: <aamelnikov@fastmail.fm>
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 1E3923A0964;
Wed, 30 Sep 2020 07:11:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.31
X-Spam-Level:
X-Spam-Status: No, score=-2.31 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, FREEMAIL_FROM=0.001,
NICE_REPLY_A=-0.213, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001,
SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key)
header.d=fastmail.fm header.b=BblAQ6m5;
dkim=pass (2048-bit key)
header.d=messagingengine.com header.b=VFT67Oqo
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 b8T3ln6wlo8G; Wed, 30 Sep 2020 07:11:44 -0700 (PDT)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com
[66.111.4.29])
(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id A4FD33A09EC;
Wed, 30 Sep 2020 07:11:44 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47])
by mailout.nyi.internal (Postfix) with ESMTP id E5C755C0069;
Wed, 30 Sep 2020 10:11:43 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162])
by compute7.internal (MEProxy); Wed, 30 Sep 2020 10:11:43 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.fm; h=
subject:to:cc:references:from:message-id:date:mime-version
:in-reply-to:content-type:content-transfer-encoding; s=fm1; bh=m
Tdh6uRsYD/P5zWLnb2DPutx5ff67tgCBc3PNQqBOEc=; b=BblAQ6m51RIakCKAf
YvcyHE7scHR5E79MOEYizy2CR8SJaqhPoKYE+ePkPvwV1E601rqosMSOfpTZwVaC
GB8OB9OWq5My8iWLNHodwvc3e0sQRiPVNWdS1Wro6sEmDBeR1GgbxTuVvrjfWqVh
2UkmAzcJw1QB2SkEqF5OngjaAwWPEZZk8eh/3xJxVHYy9jR+54hoXyB9M3ltpb/J
IzSFJlpvRcE9JT7nD0ehzI8NK0ErGkHoDCxHiBI0ox2eNRcSR43bBm0667VTCd+0
WEefbiNt/i1cNY+WB3VMWFiHQUHI40WrMG6cBXnTpC/nRz2uixkDXFEpYKNeCsUB
9CP+A==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=
messagingengine.com; h=cc:content-transfer-encoding:content-type
:date:from:in-reply-to:message-id:mime-version:references
:subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender
:x-sasl-enc; s=fm3; bh=mTdh6uRsYD/P5zWLnb2DPutx5ff67tgCBc3PNQqBO
Ec=; b=VFT67OqoGtpe0gy38IEFgTpV0icdESUqPN101+bhFvgV6H0GQuQ5THJ4B
xQZyEwOzN8wRWv6XIXp99il/+RSQ0oG8y5N3dTSDgw9OIxnsS/KYsXIUEiI2hRx8
Rdy6Zt3em36aHD9XVNYe4D10b+DVwp4cDELDmx8cPfDGooBacg4TXW1DIJ/s8dJx
TJyq+LaeFjiuGP9rXEr0uPVjjwkdcAEYS/MxEt58F3W4U/B/vtDaYvOkDAuOmFlK
wVKDGiuKxdBmMprE9jFitkbd5ZzkLJciPcayb9xoMT0XIobmgmASu+90p3Nc1O2N
p1JNjAVNR3ugsGuSqnSQanljNnQzw==
X-ME-Sender: <xms:H5J0X4GiBF3qBUBifsuetuqa4A-KbSeeMdbBvbCUy42pHzXYL3Ug8A>
<xme:H5J0XxUz27kP4tsULuSbKM2bh5sJo-dh-8V6dN8WgX7MH8kHeM20PEPcwmfmTGTMz
t6Mwi2icOHAADFTLg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedrfedvgdejtdcutefuodetggdotefrodftvf
curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu
uegrihhlohhuthemuceftddtnecunecujfgurhepuffvfhfhkffffgggjggtgfesthejre
dttdefjeenucfhrhhomheptehlvgigvgihucfovghlnhhikhhovhcuoegrrghmvghlnhhi
khhovhesfhgrshhtmhgrihhlrdhfmheqnecuggftrfgrthhtvghrnhepleduffevudevie
duteffjeffvefgtdffteduteelheejveffhfeigeekjedtteffnecukfhppeehrdekuddr
uddttddrkeeknecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrh
homheprggrmhgvlhhnihhkohhvsehfrghsthhmrghilhdrfhhm
X-ME-Proxy: <xmx:H5J0XyL29VbSwJY5sM-RP4yGySq4f56_ekWpU0rPW1IHm6dQlMBxPg>
<xmx:H5J0X6HEF6pXioKJTj2HC0Edd8proohuQPbHv0RPgX7iiImnNPIQyA>
<xmx:H5J0X-Uid-XU7kCUuIgca_iuO4hvkphMquIqJdIETW3SlIod-9Tb2g>
<xmx:H5J0X3f1ytLDUm7M_mnskoK1SGL0KK8YENvWcit3nMELpu0bBhce6w>
Received: from [192.168.1.222] (host5-81-100-88.range5-81.btcentralplus.com
[5.81.100.88])
by mail.messagingengine.com (Postfix) with ESMTPA id 997603280066;
Wed, 30 Sep 2020 10:11:42 -0400 (EDT)
To: John C Klensin <john-ietf@jck.com>, emailcore@ietf.org
Cc: ietf-smtp@ietf.org
References: <B88A405ED8AD88DA790731AB@PSB>
From: Alexey Melnikov <aamelnikov@fastmail.fm>
Message-ID: <2785867d-b5cf-523f-f99e-5e1faa285c7a@fastmail.fm>
Date: Wed, 30 Sep 2020 15:10:16 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:68.0) Gecko/20100101
Thunderbird/68.12.0
MIME-Version: 1.0
In-Reply-To: <B88A405ED8AD88DA790731AB@PSB>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/qDlH-NwDiUDUDlzlVEandsbRC54>
Subject: Re: [ietf-smtp] [Emailcore] Document updates and interactions with
the ietf-smtp mailing list
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, 30 Sep 2020 14:11:46 -0000
Hi John, On 27/09/2020 16:41, John C Klensin wrote: > (ietf-smtp@ietf.org is copied for convenience in this note -- > please do not include it in any replies.) > > Hi. > > Now that we have a WG and a separate mailing list... > > (1) The last several hours have included a discussion on > ietf-smtp about domain validation and possible modifications to > SMTP that would presumably go into 5321bis. If we are going to > have a separate mailing list for this WG, threads that propose > 5321 (or 5322) modifications should be on the emailcore list > and, if we are going to avoid very confused editors and others, > the emailcore list exclusively. I concur. I encourage people to use emailcore@ietf.org for further discussions. > I suggest that co-chairs either > take on responsibility for enforcing that principle or that they > find someone to do so. > > (2) draft-klensin-email-core-as-00 will expire this week. > Unless someone (presumably including the co-chairs) provides a > convincing argument for me to do otherwise, I do not intend to > post an updated version of that document. I would be willing to > post a version with a draft-ietf-emailcore... name, but that > means that someone needs to initiate the process of designating > it as a WG draft. And, as I have said several times before, I > don't intend to be editor of that document as it evolves with WG > discussion, so I hope the co-chairs have a volunteer to whom I > can send the XML and notes and a plan. Ack. > (3) Similarly, I do not expect there to be a > draft-klensin-rfc5321bis-04, so, if and when people want to see > an updated version of draft-klensin-rfc5321bis-03, there should > be some action to authorize posting of what would presumably be > draft-ietf-emailcore-rfc5321bis-00. Chairs will start adoption calls within a couple of weeks. Best Regards, Alexey
- [ietf-smtp] Document updates and interactions wit… John C Klensin
- Re: [ietf-smtp] [Emailcore] Document updates and … Alexey Melnikov