Received: from localhost (daemon@localhost) by cs.utk.edu with SMTP (cf v2.9s-UTK) id XAA08216; Mon, 31 Jul 2000 23:15:41 -0400 (EDT) Received: by cs.utk.edu (bulk_mailer v1.13); Mon, 31 Jul 2000 23:14:15 -0400 Received: by cs.utk.edu (cf v2.9s-UTK) id XAA08111; Mon, 31 Jul 2000 23:14:14 -0400 (EDT) Received: from playground.sun.com (marvin@localhost) by cs.utk.edu with ESMTP (cf v2.9s-UTK) id XAA08098; Mon, 31 Jul 2000 23:14:11 -0400 (EDT) Received: from playground.sun.com (192.9.5.5 -> playground.Sun.COM) by cs.utk.edu (smtpshim v1.0); Mon, 31 Jul 2000 23:14:11 -0400 Received: from opal.eng.sun.com (sun-barr.Sun.COM [192.9.9.1]) by playground.sun.com (8.11.0+Sun/8.11.0) with ESMTP id e713EAd20144; Mon, 31 Jul 2000 20:14:10 -0700 (PDT) Received: from opal (localhost [127.0.0.1]) by opal.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e713E91133801; Mon, 31 Jul 2000 20:14:09 -0700 (PDT) Message-Id: <200008010314.e713E91133801@opal.eng.sun.com> X-Mailer: exmh version 2.1.2 06/08/2000 To: Gregory Neil Shapiro cc: drums@cs.utk.edu Subject: Re: smtpupd-12: MAIL resets state tables and buffers X-Image-URL: http://playground.sun.com/~jbeck/gif/Misc/john-face.jpg In-reply-to: Your message of "Sun, 30 Jul 2000 21:39:45 PDT." <14725.785.893646.447082@monkeyboy.gshapiro.net> References: <14725.785.893646.447082@monkeyboy.gshapiro.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 31 Jul 2000 23:14:09 -0400 From: John Beck List-Unsubscribe: (Cited text modified per <14726.15246.14179.350238@horsey.gshapiro.net>) Gregory> Section 4.1.4 states, "MAIL ... MUST not be sent if a mail Gregory> transaction is already open" which I agree with. However, the Gregory> wording in 3.3 and 4.1.1.2 do not make this restriction and actually Gregory> read as if: Gregory> C: MAIL From: Gregory> S: 250 Ok Gregory> C: MAIL From: Gregory> S: 250 Ok Gregory> should be allowed an implicit RSET would be done after receiving the Gregory> second MAIL command. Gregory> Hoping that 4.1.4 is correct, this restriction should be mentioned in Gregory> sections 3.3 and 4.1.1.2. Actually, 4.1.1.2 does say: --- In general, the MAIL command may be sent only when no mail transaction is in progress, see section 4.1.4. --- So I think that section is OK. But section 3.3 says: --- This command tells the SMTP-receiver that a new mail transaction is starting and to reset all its state tables and buffers, including any recipients or mail data. --- This sounds like an implied RSET to me. So I propose modifying the first paragraph of 3.3 to: --- There are three steps to SMTP mail transactions. The transaction starts with a MAIL command which gives the sender identification. (In general, the MAIL command may be sent only when no mail transaction is in progress; see section 4.1.4.) A series of one or more RCPT commands follows giving the receiver information. Then a DATA command initiates transfer of the mail data and is terminated by the "end of mail" data indicator, which also confirms the transaction. --- -- John