OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
From: Joris Benschop (j.j.benschop_at_bio.uu.nl)
Date: Tue Feb 04 2003 - 08:19:00 CST

  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

    Hi

    Apart from trapping spam, my requirement for a FQDN HELO also seems to
    bounce some real mail. When I confronted the mail admin resposible for a
    few bounces, he claimed that *he* is following RFC, and I am not for not
    allowing the non-FQDN HELO

    My error::
    <connection from:: webmail.dds.nl (also postfix)>
    > > Out: 220 arrakis.ideeel.nl ESMTP Stichting Ideeel Internet (Postfix
    1.1.11)
    > > In: EHLO http01
    <SNIP>
    > > Out: 504 <http01>: Helo command rejected: need fully-qualified hostname

    If I'm correct, RFC-821 states that a proper HELO is required

    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.

    So; am I correct in requiring a proper HELO? How do other people handle
    these issues?

    thanks
    joris