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

Jeremy Harris <jgh@wizmail.org> Mon, 15 February 2021 23:26 UTC

Return-Path: <jgh@wizmail.org>
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 B987F3A12F2 for <emailcore@ietfa.amsl.com>; Mon, 15 Feb 2021 15:26:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (unsupported algorithm ed25519-sha256)" header.d=wizmail.org header.b=n+fXlNfX; dkim=pass (2048-bit key) header.d=wizmail.org header.b=iWDpS2xl
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 SEoyrU5ZprEz for <emailcore@ietfa.amsl.com>; Mon, 15 Feb 2021 15:26:36 -0800 (PST)
Received: from wizmail.org (wizmail.org [IPv6:2a00:1940:107::2:0:0]) (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 94B9F3A12EF for <emailcore@ietf.org>; Mon, 15 Feb 2021 15:26:35 -0800 (PST)
DKIM-Signature: v=1; a=ed25519-sha256; q=dns/txt; c=relaxed/relaxed; d=wizmail.org; s=e202001; h=Content-Transfer-Encoding:Content-Type: In-Reply-To:MIME-Version:Date:Message-ID:Subject:From:References:To:From: Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To: References:List-Id:List-Help:List-Unsubscribe:List-Subscribe:List-Post: List-Owner:List-Archive:Autocrypt; bh=sscMKHC4z9JvZn4Gmp32UpVo4bDF6MJbr8gpeE8iQ18=; b=n+fXlNfX01MYyybfCb/VXkt+mf xP8Y6kmf+4UwGxHEV7BoZ3P02QaWEQc/S/Ch1BMnYg/wli4HiXroTqskkeDw==;
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=wizmail.org ; s=r202001; h=Content-Transfer-Encoding:Content-Type:In-Reply-To: MIME-Version:Date:Message-ID:Subject:From:References:To:From:Sender:Reply-To: Subject:Date:Message-ID:To:Cc:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To: References:List-Id:List-Help:List-Unsubscribe:List-Subscribe:List-Post: List-Owner:List-Archive:Autocrypt; bh=sscMKHC4z9JvZn4Gmp32UpVo4bDF6MJbr8gpeE8iQ18=; b=iWDpS2xlDZntUGdqRomaMmhrRg lF4SAUV0gUwcTtPb6krLToqGlBcVCCeuo1jFHa4bbVZmN26bciAfW+VpSx0zmUaIMRvTFekK8RCm1 cq6fGP3rVWDGlvvPcX6jQDqVWVqHYpVdw9c6kcZI5SKPRVsSOxj5+KUTOIZlS4SrHBPMYge2HiL0m dmsIBqgGTK2ifGtWwRGoQ5aq6taCntzs48s632gG6H0B5TMeBiqB7hywdQQ8JPhQoF/uk4c8mQxg3 uQK8LIK6BUnRcFKgw+hQ8XD7yhIdGxTz6jvZSfOxx7Rznkb92Vnqe0i9Fruf8sESId2D+47hBCA9b 3pJb/jlA==;
Authentication-Results: wizmail.org; iprev=pass (vgate18.wizint.net) smtp.remote-ip=2a00:1940:107::1:2f:0; auth=pass (PLAIN) smtp.auth=jgh@wizmail.org
Received: from vgate18.wizint.net ([2a00:1940:107::1:2f:0] helo=lap.dom.ain) by wizmail.org (Exim 4.94.114) (TLS1.3) tls TLS_AES_128_GCM_SHA256 with esmtpsa id 1lBnGD-003gOh-NV for emailcore@ietf.org (return-path <jgh@wizmail.org>); Mon, 15 Feb 2021 23:26:33 +0000
To: emailcore@ietf.org
References: <ca851fda-63ac-8739-c3eb-bde725aa25f3@isode.com> <c188413b-9337-40d8-8062-9c0f58f6cd98@www.fastmail.com>
From: Jeremy Harris <jgh@wizmail.org>
Message-ID: <8874dfd9-eff4-017b-da16-81db965e8f6d@wizmail.org>
Date: Mon, 15 Feb 2021 23:26:33 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.0
MIME-Version: 1.0
In-Reply-To: <c188413b-9337-40d8-8062-9c0f58f6cd98@www.fastmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-GB
Content-Transfer-Encoding: 8bit
X-Pcms-Received-Sender: vgate18.wizint.net ([2a00:1940:107::1:2f:0] helo=lap.dom.ain) with esmtpsa
Archived-At: <https://mailarchive.ietf.org/arch/msg/emailcore/CmfxdbJwFYacwXZHTka2AI4nuss>
Subject: Re: [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: Mon, 15 Feb 2021 23:26:39 -0000

On 15/02/2021 13:41, Alexey Melnikov wrote:
>> 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?
> 
> I did a bit of digging and it doesn't look like Sendmail emits 552 or treats it as 442 if received from other MTA.
> Postfix code has this commented out with a note that this workaround creates more problems than it solves, due to other meaning of 552.
> 
> Do people have information about other MTAs (not necessarily open source) on this topic?

Exim:

  As a server, there is a configuration option (default: 452)
  for too-many-recipients.
  The documentation describing it doesn't mention standards.
  553 is emitted for other conditions.

  As a client, there is no special handling for a 552; the initial
  5 is taken as for any other 5xx.
-- 
Cheers,
   Jeremy