Re: RFC2821bis-01 Issue 4: Client actions on receipt of 4yz and 5yz cod

ietf-smtp

Re: RFC2821bis-01 Issue 4: Client actions on receipt of 4yz and 5yz codes

2007-03-29 12:02:50


Tony Hansen wrote:

Any comments?


"SHOULD NOT repeat" is clearer than "discouraged from repeating".

It still allows some wiggle room for what constitutes "repeating
the exact request (in the same sequence)".  Trying less RCPT TO
before a DATA isn't the same sequence, or is it ?

Frank

[More with this subject...]

<Prev in Thread]	Current Thread	[Next in Thread>
RFC2821bis-01 Issue 4: Client actions on receipt of 4yz and 5yz codes, John C Klensin Re: RFC2821bis-01 Issue 4: Client actions on receipt of 4yz and 5yz codes, Tony Hansen Re: RFC2821bis-01 Issue 4: Client actions on receipt of 4yz and 5yz codes, Hector Santos Re: RFC2821bis-01 Issue 4: Client actions on receipt of 4yz and 5yz codes, John C Klensin Re: RFC2821bis-01 Issue 4: Client actions on receipt of 4yz and 5yz codes, Peter J. Holzer Re: RFC2821bis-01 Issue 4: Client actions on receipt of 4yz and 5yz codes, David F. Skoll Re: RFC2821bis-01 Issue 4: Client actions on receipt of 4yz and 5yz codes, Frank Ellermann <=

Previous by Date:	Re: RFC2821bis-01 Issue 3: EHLO parameter, Robert A. Rosenberg
Next by Date:	Re: RFC2821bis-01 Issue 3: EHLO parameter, John C Klensin
Previous by Thread:	Re: RFC2821bis-01 Issue 4: Client actions on receipt of 4yz and 5yz codes, David F. Skoll
Next by Thread:	RFC2821bis-01 Issue 3: EHLO parameter, John C Klensin
Indexes:	[Date] [Thread] [Top] [All Lists]