Re: [Emailcore] Two extra issues

[Ned Freed <[e-mail]>]

> In article <9ABCA62E3E54C4356D09E1EE@PSB> you write:
> >Hi.
> >
> >As mentioned in my note about ticket #2 sent about an hour ago,
> >two additional issues came to my attention (or I was reminded
> >about them) while looking at that issue and looking through the
> >document.
> >
> >I've put them into the working version of what will become
> >draft-ietf-emailcore-rfc5321bis-01 as:
> >
> >       ----
> >
> > G.12.  Extension Keywords Starting in 'X-'

> Kill them.

> > G.13.  Deprecating HELO

> >   discussion on the EMAILCORE list, should EHLO be explicitly bound to
> >   SMTP over TCP with the older transports allowed only with HELO?

> I am pretty sure that all of the other transports described in RFC 821
> are dead, or close enough (X.25, where it says to run TCP over it.)

I haven't seen an alternate transport in use in a long time.

> Is anyone here aware of running SMTP over anything else, and if so
> using HELO rather than EHLO? I'm not.

There's still quite a few HELO's being sent by IOT stuff that supports email.
And I can understand why - when every byte counts, code to fall back from EHLO
to HELO isn't going to be written.

And as luck would have it only yesterday I had a request for the option in our
server to disable client use of EHLO. I guess something couldn't tolerate it.
(Yes, I had to look it up.)

				Ned