IETF Logo Mail Archive

[Emailcore] Ticket #5: G.5. Remove or deprecate the work-around from code 552 to 452?

Alexey Melnikov <alexey.melnikov@isode.com> Tue, 19 January 2021 16:24 UTC

Return-Path: <alexey.melnikov@isode.com>
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 ECE4C3A15F0 for <emailcore@ietfa.amsl.com>; Tue, 19 Jan 2021 08:24:58 -0800 (PST)
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, 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 giWosM_57le0 for <emailcore@ietfa.amsl.com>; Tue, 19 Jan 2021 08:24:58 -0800 (PST)
Received: from statler.isode.com (Statler.isode.com [62.232.206.189]) by ietfa.amsl.com (Postfix) with ESMTP id EADF33A15EB for <emailcore@ietf.org>; Tue, 19 Jan 2021 08:24:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1611073497; d=isode.com; s=june2016; i=@isode.com; bh=B9oiQr1byktSrFu2z/HjdrrzAV4zaVBAM3Nv7z8mZ84=; 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=p4LKnTM2ZohhFyoRKHVaDaK/FId+/jIXiqn7NB0PyDSCg8KVBxrJf1ArmFdRkYzfm/zPPU Ov1qa7mF5pegCiDAXyqRuMJ3X/aHnDarha+Bzhzzqi/6EPxf4w/k2UVV4NAYwoTmTBfdLU 1EkBoSImqibwT26Rzhw5iVucOkw+wMU=;
Received: from [172.27.250.167] (connect.isode.net [172.20.0.72]) by statler.isode.com (submission channel) via TCP with ESMTPSA id <YAcH2ABqmnqY@statler.isode.com>; Tue, 19 Jan 2021 16:24:56 +0000
To: emailcore@ietf.org
From: Alexey Melnikov <alexey.melnikov@isode.com>
Message-ID: <ca851fda-63ac-8739-c3eb-bde725aa25f3@isode.com>
Date: Tue, 19 Jan 2021 16:24:55 +0000
User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-GB
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/emailcore/IREZktaUrAyUD1zbnl9x-5QR1vI>
Subject: [Emailcore] Ticket #5: G.5. Remove or deprecate the work-around from code 552 to 452?
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 16:24:59 -0000

Hi all,

The first pagaraph of Section 4.5.3.1.10 (Too Many Recipients Code) 
currently says:

    RFC 821 [3] incorrectly listed the error where an SMTP server
    exhausts its implementation limit on the number of RCPT commands
    ("too many recipients") as having reply code 552.  The correct reply
    code for this condition is 452.  Clients SHOULD treat a 552 code in
    this case as a temporary, rather than permanent, failure so the logic
    below works.

John noted that this suggestion may have outlived its usefulness
and/or be inconsistent with current practice. Should it be removed
and/or explicitly deprecated?

Best Regards,

Alexey

v2.23.0 | Report a Bug | By Email