Re: STARTTLS & EHLO: Errata text?

Hector Santos <hsantos@santronics.com> Fri, 30 January 2009 00:22 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 n0U0MdfW048205 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 29 Jan 2009 17:22:39 -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 n0U0MdXS048204; Thu, 29 Jan 2009 17:22:39 -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 winserver.com (news.winserver.com [208.247.131.9]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n0U0Mcs4048198 for <ietf-smtp@imc.org>; Thu, 29 Jan 2009 17:22:38 -0700 (MST) (envelope-from hsantos@santronics.com)
Received: by winserver.com (Wildcat! SMTP Router v6.3.452.5) for ietf-smtp@imc.org; Thu, 29 Jan 2009 19:02:33 -0500
Received: from hdev1 ([65.10.45.22]) by winserver.com (Wildcat! SMTP v6.3.452.5) with ESMTP id 2759575156; Thu, 29 Jan 2009 19:02:32 -0500
Message-ID: <49824369.3060206@santronics.com>
Date: Thu, 29 Jan 2009 19:01:45 -0500
From: Hector Santos <hsantos@santronics.com>
Organization: Santronics Software, Inc.
User-Agent: Thunderbird 2.0.0.0 (Windows/20070326)
MIME-Version: 1.0
To: SM <sm@resistor.net>
CC: Ned Freed <ned.freed@mrochek.com>, ietf-smtp@imc.org
Subject: Re: STARTTLS & EHLO: Errata text?
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> <6.2.5.6.2.20090129094120.02f234a0@resistor.net> <01N4VB00O5UQ00007A@mauve.mrochek.com> <6.2.5.6.2.20090129142242.02ef4a60@resistor.net>
In-Reply-To: <6.2.5.6.2.20090129142242.02ef4a60@resistor.net>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
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>

SM wrote:

> One of the questions was about the "The client SHOULD send an EHLO 
> command as the first command after a successful TLS negotiation."  As 
> with everything SMTP, there are two sides, the sender and the receiver.  
> Instead of thinking in terms of whether the sender should send the 
> command, we could look at this in terms of whether the receiver must 
> accept a mail transaction without being sent an EHLO command.  I don't 
> see anything in the specifications that say that.

The more I think about this, I think its just all fine.  We had one 
client presented here who failed to reissue a EHLO/HELO as expected in 
practice.  The server issues a negative response and the client failed 
to continue properly.  Even if the implementer read 3207 as a SHOULD, 
that alone should be enough to tell the client that it MAY have to 
reissue the EHLO/HELO if the MAIL FROM: command failed.

In other words,

   SHOULD says "Be Prepared To Reissue EHLO/HELO"

There is nothing that says that it does not need to send it and abort 
the transaction if the server requires it.

-- 
Sincerely

Hector Santos, CTO
http://www.santronics.com
http://santronics.blogspot.com