Re: RSET scope issue

Chris Newman <cnewman@innosoft.com> Wed, 16 August 2000 01:34 UTC

Received: from cs.utk.edu (CS.UTK.EDU [128.169.94.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA03364 for <drums-archive@odin.ietf.org>; Tue, 15 Aug 2000 21:34:03 -0400 (EDT)
Received: from localhost (daemon@localhost) by cs.utk.edu with SMTP (cf v2.9s-UTK) id VAA06777; Tue, 15 Aug 2000 21:33:48 -0400 (EDT)
Received: by cs.utk.edu (bulk_mailer v1.13); Tue, 15 Aug 2000 21:33:42 -0400
Received: by cs.utk.edu (cf v2.9s-UTK) id VAA06751; Tue, 15 Aug 2000 21:33:41 -0400 (EDT)
Received: from mercury.Sun.COM (marvin@localhost) by cs.utk.edu with ESMTP (cf v2.9s-UTK) id VAA06733; Tue, 15 Aug 2000 21:33:39 -0400 (EDT)
Received: from mercury.Sun.COM (192.9.25.1 -> mercury.Sun.COM) by cs.utk.edu (smtpshim v1.0); Tue, 15 Aug 2000 21:33:39 -0400
Received: from westmail2.West.Sun.COM ([129.153.100.30]) by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id SAA17603; Tue, 15 Aug 2000 18:33:37 -0700 (PDT)
Received: from nifty-jr.west.sun.com (nifty-jr.West.Sun.COM [129.153.12.95]) by westmail2.West.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id SAA26271; Tue, 15 Aug 2000 18:33:37 -0700 (PDT)
Date: Tue, 15 Aug 2000 18:32:26 -0700
From: Chris Newman <cnewman@innosoft.com>
To: Philip Hazel <ph10@cus.cam.ac.uk>
cc: Detailed Revision/Update of Message Standards <drums@cs.utk.edu>
Subject: Re: RSET scope issue
Message-ID: <4003837.3175353146@nifty-jr.west.sun.com>
In-Reply-To: <Pine.SOL.4.21.0008150855480.17461-100000@draco.cus.cam.ac.uk>
X-Mailer: Mulberry/2.0.3 (MacOS)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
List-Unsubscribe: <mailto:drums-request@cs.utk.edu?Subject=unsubscribe>
Content-Transfer-Encoding: 7bit

--On Tuesday, August 15, 2000 9:03 +0100 Philip Hazel <ph10@cus.cam.ac.uk> 
wrote:
> usually "specify", and the use of the future tense reads oddly.) Here is
> a minor revision:
>
>    This command causes the current mail transaction to be aborted. It
>    resets the state to what it was at the beginning of the transaction.
>    The state of the connection itself is not affected. Any stored sender
>    .... etc.

I object to this proposed change.

Take command sequence:

MAIL FROM:<loser@nowhere.org>
MAIL FROM:<bozo@somewhere.com>
RSET

Unless we explicitly add language to the SMTP spec which states that a 
"MAIL FROM" MUST return a 503 error when a transaction is in progress, then 
the second sentence in the proposed text is factually incorrect (or at best 
in a gray area).  Given what 821 says about "MAIL FROM" doing an implied 
reset and the fact 503 is not listed as a valid response to "MAIL" in 821, 
I can't see a justification for such a drastic reversal.

Because a mail transaction is arguably part of the connection state, the 
third sentence could be seen as contradictory to the first sentence.

Given how hard it is to get wording right in this area and how late we are, 
I'd prefer to just delete the offending sentence and be done with it.

		- Chris (speaking for myself only)