Julian Mehnle wrote:
it depends on _why_ the first HELO/EHLO command was rejected.
One simple reason why a EHLO can be rejected is if the server
doesn't talk ESMTP. Then the client can simply try HELO or
IIRC maybe RSET followed by HELO. In that case the "second"
HELO (actually the first after EHLO didn't work) is "the" HELO.
So maybe there can be sequences of mutiple EHLO/HELO, all but
the last one failing for various reasons. The last EHLO/HELO
finally makes it and is "the" HELO id.
Is it possible to send more than one accepted EHLO/HELO ? Or
is that always "5xx invalid sequence of commands" ? If it is
an invalid sequence of commands, can RSET reset it, or is the
only exit QUIT + new connection ?
I'm to lazy to check it. But IIRC there's no such thing as
"try pipelining". If a client wants that it "must" wait until
the EHLO is accepted and "pipelining" allowed. That "must"
could be a bad case of "in theory" ;-)
But it wouldn't surprise me if more than one accepted EHLO/HELO
per connection is just invalid. If the server does it anyway
it should check any accepted HELO. Otherwise the one and only
accepted EHLO/HELO should be "the" HELO id. wrt SPF.
Bye, Frank
-------
Sender Policy Framework: http://www.openspf.org/
Archives at http://archives.listbox.com/spf-discuss/current/
To unsubscribe, change your address, or temporarily deactivate your
subscription,
please go to
http://v2.listbox.com/member/?listname=spf-discuss(_at_)v2(_dot_)listbox(_dot_)com