Re: RFC2821, section 4.1.1.1 and HELO/EHLO

On Fri, 2004-01-02 at 18:50, Valdis(_dot_)Kletnieks(_at_)vt(_dot_)edu wrote:
> By my reading, this allows 'ehlo F.Q.D.N' and 'ehlo [add.ress.lit.eral]', but
> there is no way to actually generate 'optionally followed by information' 
> using
> the ABNF as written.
>
> Am I caffeine-challenged, or is the ABNF actually borked on this?
I'd say it's section 4.1.1.1 that's b0rked. If you allow free
form "information" after the FQDN/address-literal it makes it
impossible to parse (ESMTP) parameters for EHLO.


        Bob

-- 
-=[ B. Johannessen | bob(_at_)db(_dot_)org -=- http://db.org/ | +4797152009 ]=-
-=[ Mail & Spam - News, Drafts & Standards - http://db.org/blog/ ]=-