IETF Logo Mail Archive

Re: STARTTLS & EHLO: Errata text?

John C Klensin <john+smtp@jck.com> Sun, 01 February 2009 17:49 UTC

Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n11HnZml098778 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 1 Feb 2009 10:49:35 -0700 (MST) (envelope-from owner-ietf-smtp@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n11HnZpA098777; Sun, 1 Feb 2009 10:49:35 -0700 (MST) (envelope-from owner-ietf-smtp@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-smtp@mail.imc.org using -f
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n11HnY65098770 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for <ietf-smtp@imc.org>; Sun, 1 Feb 2009 10:49:35 -0700 (MST) (envelope-from john+smtp@jck.com)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1LTgRg-0000kj-6X; Sun, 01 Feb 2009 12:49:24 -0500
Date: Sun, 01 Feb 2009 12:49:23 -0500
From: John C Klensin <john+smtp@jck.com>
To: Tony Finch <dot@dotat.at>, Hector Santos <hsantos@santronics.com>
cc: ietf-smtp@imc.org
Subject: Re: STARTTLS & EHLO: Errata text?
Message-ID: <AE5689449BAC89829F0DD5E7@PST.JCK.COM>
In-Reply-To: <alpine.LSU.2.00.0902011706190.10756@hermes-2.csi.cam.ac.uk>
References: <497DE492.4080506@pscs.co.uk> <497DED29.70402@att.com> <497ED420.30708@pscs.co.uk> <alpine.LSU.2.00.0901271403220.4546@hermes-2.csi.cam.ac.uk> <497F86CB.60904@att.com> <alpine.LSU.2.00.0901281434440.4546@hermes-2.csi.cam.ac.uk> <498088B8.9040404@pscs.co.uk> <alpine.LSU.2.00.0901291310080.4546@hermes-2.csi.cam.ac.uk> <4981C0D5.1010401@pscs.co.uk> <4981C6BD.2040900@att.com> <37F39FF37390694B69567838@PST.JCK.COM> <4981E1AB.9000002@att.com> <alpine.LSU.2.00.0901301832470.4795@hermes-2.csi.cam.ac.uk> <49835DE2.3030403@santronics.com> <alpine.LSU.2.00.0901312021190.14750@hermes-2.csi.cam.ac.uk> <4984C49C.5030401@santronics.com> <alpine.LSU.2.00.0902011706190.10756@hermes-2.csi.cam.ac.uk>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-ietf-smtp@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-smtp/mail-archive/>
List-ID: <ietf-smtp.imc.org>
List-Unsubscribe: <mailto:ietf-smtp-request@imc.org?body=unsubscribe>

--On Sunday, February 01, 2009 17:14 +0000 Tony Finch
<dot@dotat.at> wrote:

> 
> On Sat, 31 Jan 2009, Hector Santos wrote:
>> 
>> So the one question I did have was the response code from the
>> server.  As shown, the server issued 550. It was something:
>> 
>>    [TLS established]
>>    C: MAIL FROM <xxxx>
>>    S: 550 EHLO/HELO required.
>> 
>> Shouldn't the server response be 503 (Bad Sequence of
>> commands)?
>... 
>> If so, should this be stated in the revised text?
> 
> Not in 3207 - this requirement is inherited from 5321.

IMO, that requirement, and the use of the codes, is perfectly
clear in 5321 (at least to anyone who bothers to read it).  If
someone disagrees, please send text.

    john

v2.23.0 | Report a Bug | By Email