Valdis(_dot_)Kletnieks(_at_)vt(_dot_)edu wrote:
On Sun, 24 Feb 2008 16:16:02 EST, Hector Santos said:
S: 220 **************************************************
C: EHLO yyyyyyy.com
S: 500 Syntax error, command unrecognized
Am I the only one who thinks that if the remote end doesn't understand
EHLO, it's highly unlikely that any revision of 2821 is going to improve
matters? RFC1425 was a *long* time ago....
Agree.
However, all this is based on the presumption everyone is operating with
Contemporary (actively supported) SMTP systems.
So any issue or problem is not with active systems. They can adjust as
was the case here with this particular vendor.
It is also not an issue with old, no longer supported, legacy SMTP
SERVERS because they may not have a mean of changing. e.g., the authors
may be dead and bury, gone or whatever. They are out of the loop or some
low budget business found some cheap old SMTP software, who knows.
But rather the burden is with current, actively supported SMTP clients
because it is they who will have to deal with such situations.
PS: EHLO/HELO fall back happens all the time with even contemporary
systems especially among many who are using AVS proxies.
--
Sincerely
Hector Santos, CTO
http://www.santronics.com
http://santronics.blogspot.com