Re: smtpupd-12: MAIL resets state tables and buffers

[John Beck <[e-mail]>]

(Cited text modified per <[e-mail]>)

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:<[e-mail]>
Gregory> S: 250 Ok
Gregory> C: MAIL From:<[e-mail]>
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