Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email email@example.com
From: pw (p.willistelus.net)
Date: Fri May 16 2008 - 15:13:51 CDT
> pw wrote:
>> Why does postfix **NOT** send
>> '250 OK'
>> after EHLO has finished dumping server info?
>> According to RFC-821 '250 OK' should be returned
>> after **ALL** successful commands.
>> RFC-1869 does not invalidate the basic handshaking of
>> When testing postfix SMTP I get no '250 OK'
>> after EHLO.
>> Am I missing a config file flag somewhere, or
>> is postfix a faulty mail server?
> if I connect to postfix, send an EHLO command and disconnect my cable, I
> don't get a response. but this has never been a problem for me.
> if you notice a problem, please describe exactly what you do, what you
> see, what you get, ... etc.
> anyway, postfix does respond to the HELO/EHLO command. and this is why a
> lot of people get mail!
Yes, when you send EHLO you get extended information. A list. That's
fine, it should do that. However, after the list of extended information
has finished, what indication does the server give (other than waitng)
that the list has ended and the server is once again in a ready state
for another command?
'250 OK' would indicate that the server has completed the extended
information and is ready for another command.
From a programmatic viewpoint we can just keep reading
'250 <arbitrary_text>' lines until they stop coming, then
give the next command. It is, however, difficult for a client
to differentiate between a state where the server has paused
between extended server information lines and the actual end of
extended server information.
Thus, my point was the lack of '250 OK', after the end
of the extended information list, appears to be arbitrary