[yam] [Fwd: RFC 5321, Erratum 1543]

Alexey Melnikov <alexey.melnikov@isode.com> Mon, 07 September 2009 09:38 UTC

Return-Path: <alexey.melnikov@isode.com>
X-Original-To: yam@core3.amsl.com
Delivered-To: yam@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C44F73A67E5 for <yam@core3.amsl.com>; Mon, 7 Sep 2009 02:38:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.544
X-Spam-Level:
X-Spam-Status: No, score=-2.544 tagged_above=-999 required=5 tests=[AWL=0.055, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HS8engnm2K44 for <yam@core3.amsl.com>; Mon, 7 Sep 2009 02:38:24 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id EF7403A68F1 for <yam@ietf.org>; Mon, 7 Sep 2009 02:38:22 -0700 (PDT)
Received: from [172.16.2.139] (shiny.isode.com [62.3.217.250]) by rufus.isode.com (submission channel) via TCP with ESMTPA id <SqTUpwB9YWix@rufus.isode.com>; Mon, 7 Sep 2009 10:38:47 +0100
Message-ID: <4AA4D490.9020700@isode.com>
Date: Mon, 07 Sep 2009 10:38:24 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: yam@ietf.org
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="------------000807080507040000090503"
Subject: [yam] [Fwd: RFC 5321, Erratum 1543]
X-BeenThere: yam@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Yet Another Mail working group discussion list <yam.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/yam>, <mailto:yam-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/yam>
List-Post: <mailto:yam@ietf.org>
List-Help: <mailto:yam-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yam>, <mailto:yam-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Sep 2009 09:38:24 -0000

John suggested that I forward this to the YAM mailing list.

--- Begin Message ---
John,
Can you tell me if you think this one is correct?

> Reported By: Brett Watson
> Date Reported: 2008-10-08
>
> Section 3.8 says:
>
>   SMTP clients that experience a connection close, reset, or other
>   communications failure due to circumstances not under their control
>   (in violation of the intent of this specification but sometimes
>   unavoidable) SHOULD, to maintain the robustness of the mail system,
>   treat the mail transaction as if a 451 response had been received and
>   act accordingly.
>
>  
>
> It should say:
>
>   SMTP clients that experience a connection close, reset, or other
>   communications failure due to circumstances not under their control
>   (in violation of the intent of this specification but sometimes
>   unavoidable) SHOULD, to maintain the robustness of the mail system,
>   treat the mail transaction as if a 421 response had been received and
>   act accordingly.
>
>  
>
> Notes:
>
> SMTP clients are told to act as though a 451 response ("Requested 
> action aborted: local error in processing") had been received when 
> context clearly indicates that a 421 response ("Service not available, 
> closing transmission channel") was intended.
>

--- End Message ---