[Raw Msg Headers][Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Does the EHLO response break RFC2821 syntax?
Hi, I've just started using ZMailer. I'm using version 2.99.57-pre4 on
a Solaris 9 SPARC.
If a EHLO command is issued by the client, without the required domain
parameter, then ZMailer still accepts it and returns a 250 response, no
problem.
However, the 250 response contains a error message as follows:
>220 localhost ZMailer Server 2.99.57.pre4 #1 ESMTP ready at Fri, 12 May
>2006 10:57:20 +0000
>ehlo
>250-Invalid `ehlo' parameter!
>250-5.7.1 Sorry [127.0.0.1], Err: RFC821: No input
>250-localhost expected "EHLO localhost"
>250-SIZE 0
>250-8BITMIME
>250-PIPELINING
>250-CHUNKING
>250-ENHANCEDSTATUSCODES
>250-DSN
>250-X-RCPTLIMIT 10000
>250-ETRN
>250 HELP
This seems to me to be a breach of RFC2821 syntax
> ehlo-ok-rsp = ( "250" domain [ SP ehlo-greet ] CRLF )
> / ( "250-" domain [ SP ehlo-greet ] CRLF
> *( "250-" ehlo-line CRLF )
> "250" SP ehlo-line CRLF )
>
> ehlo-greet = 1*(%d0-9 / %d11-12 / %d14-127)
> ; string of any characters other than CR or LF
>
> ehlo-line = ehlo-keyword *( SP ehlo-param )
>
> ehlo-keyword = (ALPHA / DIGIT) *(ALPHA / DIGIT / "-")
> ; additional syntax of ehlo-params depends on
> ; ehlo-keyword
None of the three error message lines above conform to the ehlo-line
syntax, a breach of RFC2821.
Surely, if ZMailer wishes to return an error message in this case then
shouldn't it be contained in the ehlo-greet part of the response, and
not in an ehlo-line?
Or have I misconfigured ZMailer?
Regards
--
Paul Overell Internet Platform Development Manager, Thus plc
-
To unsubscribe from this list: send the line "unsubscribe zmailer" in
the body of a message to majordomo@nic.funet.fi