Re: [Emailcore] Ticket #13: G.7.7. Does the 'first digit only' and/or non-listed reply code text need clarification?

Dave Crocker <dhc@dcrocker.net> Tue, 19 January 2021 15:32 UTC

Return-Path: <dhc@dcrocker.net>
X-Original-To: emailcore@ietfa.amsl.com
Delivered-To: emailcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BC953A15B5 for <emailcore@ietfa.amsl.com>; Tue, 19 Jan 2021 07:32:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.361
X-Spam-Level:
X-Spam-Status: No, score=-2.361 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, NICE_REPLY_A=-0.262, 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 (2048-bit key) header.d=dcrocker.net
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 qxSTPekvHSGB for <emailcore@ietfa.amsl.com>; Tue, 19 Jan 2021 07:32:16 -0800 (PST)
Received: from coral.ash.relay.mailchannels.net (coral.ash.relay.mailchannels.net [23.83.222.39]) (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 A50263A08D6 for <emailcore@ietf.org>; Tue, 19 Jan 2021 07:32:14 -0800 (PST)
X-Sender-Id: hostingeremail|x-authsender|dhc@dcrocker.net
Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id 560CF23029; Tue, 19 Jan 2021 15:32:11 +0000 (UTC)
Received: from nl-srv-smtpout1.hostinger.io (100-96-87-139.trex.outbound.svc.cluster.local [100.96.87.139]) (Authenticated sender: hostingeremail) by relay.mailchannels.net (Postfix) with ESMTPA id 298B7204EC; Tue, 19 Jan 2021 15:31:59 +0000 (UTC)
X-Sender-Id: hostingeremail|x-authsender|dhc@dcrocker.net
Received: from nl-srv-smtpout1.hostinger.io ([UNAVAILABLE]. [185.224.136.7]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:2500 (trex/6.0.1); Tue, 19 Jan 2021 15:32:11 +0000
X-MC-Relay: Neutral
X-MailChannels-SenderId: hostingeremail|x-authsender|dhc@dcrocker.net
X-MailChannels-Auth-Id: hostingeremail
X-Cellar-Well-Made: 65c34e946322678a_1611070321016_1556498924
X-MC-Loop-Signature: 1611070321016:3026152204
X-MC-Ingress-Time: 1611070321015
Received: from [192.168.0.109] (c-24-130-62-181.hsd1.ca.comcast.net [24.130.62.181]) (Authenticated sender: dhc@dcrocker.net) by nl-srv-smtpout1.hostinger.io (smtp.hostinger.com) with ESMTPSA id A149F20297F3; Tue, 19 Jan 2021 15:31:53 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=hostingermail-a; t=1611070317; bh=QsJwj19ADRT2psTGx2fPeIP/nodu8wAcqtiQHhIu2bk=; h=Reply-To:Subject:To:Cc:References:From:Date:In-Reply-To; b=XnuWjgSEwtbm3Dr+JqtRHbo1ta86gapv8+r/GPLWPV90ubvNcr/dI14ofYehEE7yx a6eP1r97JAJxScfgI1o3Hdnwoz1N11qKMGy8s50jsv0s8AJBCQo4H/wn5X+MvyKeVb huUw8GhZ990xXdklfTyul+ZGT5O2p98FUTEumC9S4Prjr3K8RtDs89sonLldqcn4Sd YgJk1QmawqKsCbArqXwJx7oZZ0EWp6UIBJTynvreNDShKB6TxYmeZsCpBO4GqUyoHk DkEBaZhWAupQI6DNr3u8TQhkIHd4zmudGjqWBC7dyrdj2oY1WvUmBUXQf1qsxPXYLx eWyoXFyejr/7A==
Reply-To: dcrocker@bbiw.net
To: Alexey Melnikov <aamelnikov@fastmail.fm>, Alessandro Vesely <vesely@tana.it>, John C Klensin <john-ietf@jck.com>
Cc: emailcore@ietf.org
References: <20201217034150.AA9142AC1E50@ary.qy> <76CF0B1097EB28A5BDE902EE@PSB> <47407afa-6e6a-d0d2-a829-67d68fd0ee90@tana.it> <f99fb03d-f1ef-4b71-8731-5933026db5ce@www.fastmail.com>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <8a9a363a-68dd-80ed-2ff2-b4d19fb74359@dcrocker.net>
Date: Tue, 19 Jan 2021 07:31:50 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.6.1
MIME-Version: 1.0
In-Reply-To: <f99fb03d-f1ef-4b71-8731-5933026db5ce@www.fastmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/emailcore/Ib_Jg546vrA4P376GCTeIMEvpCs>
Subject: Re: [Emailcore] Ticket #13: G.7.7. Does the 'first digit only' and/or non-listed reply code text need clarification?
X-BeenThere: emailcore@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: EMAILCORE proposed working group list <emailcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emailcore>, <mailto:emailcore-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emailcore/>
List-Post: <mailto:emailcore@ietf.org>
List-Help: <mailto:emailcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emailcore>, <mailto:emailcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Jan 2021 15:32:18 -0000

On 1/19/2021 7:23 AM, Alexey Melnikov wrote:
> NEW: Sender-SMTP tests the whole 3 digit reply code it receives and 
> any supplemental codes or information (see RFC 3463 and RFC 5248) if
>  it recognizes them. Sender-SMTP MUST use the first digit (severity 
> indication) of a reply code it receives if the full reply code or 
> additional information is not recognized.


Given the normative term in the second sentence it seems odd -- and
possibly problematic -- to have no normative term in the first sentence.


I assume the intention here is:

     Sender-SMTP MUST first test the whole 3 digit reply code it
receives, as well as any accompanying supplemental codes or information
(see RFC 3463 and RFC 5248). If the full reply code or additional
information is not recognized, Sender-SMTP MUST use the first digit
(severity indication) of a reply code it receives


d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net