I've now run into 2 universities that are blocking email based on invalid hostnames at the HELO sequence.
From what I can see with RFC1123, (see http://www.freesoft.org/CIE/RFC/1123/90.htm) this seems to be a no-no.
5.2.5 HELO Command: RFC-821 Section 3.5
The 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 really corresponds 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).
I'd ask the sendmail usenet group - but it tends to be clogged with more neophyte questions... plus, this item is about spam control which is more on que with what most of us do here with sendmail - so I'm hoping for a more solid answer based on use than user-guides.
Thanks,
-Ben
_______________________________________________ Visit http://www.mimedefang.org and http://www.canit.ca MIMEDefang mailing list [email protected] http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
