Hi friends,I have found this RFC, wich say that HELO/EHLO command should be execute with <domain sender> parameter:Example:Good use: >HELO domain.com >EHLO domain.comBad use >HELO 501 #5.0.0 EHLO requires domain address >EHLO 501 #5.0.0 EHLO requires domain addressHave you any patch for qmail-ldap for compliant with this RFC??--Here the HELO section of RFC1123:
5.2.5 HELO Command: RFC-821[1] Section 3.5The sender-SMTP MUST ensure that the <domain> parameter in a HELO command is a valid principal host domain name for the client host. As a result, the receiver-SMTP will not have to perform MX resolution on this name in order to validate the HELO parameter.The HELO receiver MAY verify that the HELO parameter reallyRFC1123[2] MAIL -- SMTP & RFC-822[3] October 1989corresponds to the IP address of the sender. However, the receiver MUST NOT refuse to accept a message, even if the sender's HELO command fails verification.DISCUSSION: Verifying the HELO parameter requires a domain name lookup and may therefore take considerable time. An alternative tool for tracking bogus mail sources is suggested below (see "DATA Command").Note also that the HELO argument is still required to have valid <domain> syntax, since it will appear in a Received: line; otherwise, a 501 error is to be sent.IMPLEMENTATION: When HELO parameter validation fails, a suggested procedure is to insert a note about the unknown authenticity of the sender into the message header (e.g., in the "Received:" line). VÃnculos: --------- [1] http://www.faqs.org/rfcs/rfc821.html [2] http://www.faqs.org/rfcs/rfc1123.html [3] http://www.faqs.org/rfcs/rfc822.html
