|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
From: pw (p.willis
telus.net)
Date: Fri May 16 2008 - 15:32:49 CDT
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
mouss wrote:
>
> please read the RFCs. the last "response" has no '-' after the status code.
>
> 220- ...
> 220- ...
> ...
> 220 blah blah
>
> do you see the '-' after 220 in all but the last line?
>
<////////>
> you need to check the 4th character. see above.
>
>
Thank you, you are correct. I now see what the client should
be looking for.
I thought the hyphen was *also* arbitrary text, but
it's actually the spacer.
<EXCERPT>
Normally, the response to EHLO will be a multiline reply. Each line
of the response contains a keyword and, optionally, one or more
parameters. Following the normal syntax for multiline replies, these
keyworks follow the code (250) and a hyphen for all but the last
line, and the code and a space for the last line.
</EXCERPT>
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]