Announcement

Collapse
No announcement yet.

HELO/EHLO SMTP PROBLEMS.. Exchange 2007

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • HELO/EHLO SMTP PROBLEMS.. Exchange 2007

    Few days ago I got blacklist due to the fact that the HELO response of my SMTP is NAME.DOMAIN.local ([127.0.0.1]) by NAME
    ([127.0.0.1]) with mapi; Tue, ETC ETC...

    Under EMC, I went to Server Configuration->Hub Transport->Default NAME

    click on properties and tried to change the specified FQDN from NAME.DOMAIN.local to mail.xxx.com

    Unfortunately I get this replied..

    set-receiveconnector
    Failed
    Error:
    When the AuthMechanism parameter on a Receive connector is set to the value ExchangeServer, you must set the FQDN parameter on the Receive connector to one of the following values: the FQDN of the transport server "Name.DOMAIN.local", the NetBIOS name of the transport server "NAME", or $null.


    Any ideas where to go from here???

    Thx

  • #2
    Re: HELO/EHLO SMTP PROBLEMS.. Exchange 2007

    Wanted to add this as well....

    I went to Organization Configuration->Hub Transport->Send Connectors
    Under properties it shows the correct FQDN mail.domain.com

    Comment


    • #3
      Re: HELO/EHLO SMTP PROBLEMS.. Exchange 2007

      Who blacklisted you?
      The response to a TELNET on port 25, is different to outbound email. The receive connector is all that any automated tests can connect to, and that should be either <null>, the server's name or the server's FQDN. Anything else is going to cause problems. Change it back to the default settings.

      Anyone blacklisting based on the ehlo response on INBOUND email is stupid, and I am not aware of any blacklists working in that way.

      The most common reason for ehlo blacklisting is because your ehlo on the send connector does NOT resolve to the same IP address that the traffic is coming from and/or does not have a matching PTR (Aka reverse DNS).

      Simon.
      --
      Simon Butler
      Exchange MVP

      Blog: http://blog.sembee.co.uk/
      More Exchange Content: http://exchange.sembee.info/
      Exchange Resources List: http://exbpa.com/
      In the UK? Hire me: http://www.sembee.co.uk/

      Sembee is a registered trademark, used here with permission.

      Comment


      • #4
        Re: HELO/EHLO SMTP PROBLEMS.. Exchange 2007

        CBL and SPAMHAUS.... I was rejected in a few popular domains, such as Hotmail, prodigy, etc....

        So what I need to know is how I can change the HELO from replying

        (BANNER) 220 server1.mydomain.local Microsoft ESMTP MAIL Service ready at Wed, 9 Jan
        2013 08:30:07 -0800


        HELO
        250 server1.mydomain.local Hello [10.29.10.3]

        to

        server1.mydomain.com [216.64.xxx.xxx]


        ?????????

        Comment


        • #5
          Re: HELO/EHLO SMTP PROBLEMS.. Exchange 2007

          I know a telnet can't tell me what I need to know, but either way mxtoolbox sees me like this

          Received: from server1.mydomain.local ([127.0.0.1]) by server1
          ([127.0.0.1]) with mapi; Wed, 9 Jan 2013 08:36:56 -0800

          Comment


          • #6
            Re: HELO/EHLO SMTP PROBLEMS.. Exchange 2007

            There is nothing that you can do.
            The tests on sites such as MXTOOLBOX give false results.
            http://blog.sembee.co.uk/post/Exchan...ner-Tests.aspx

            The FQDN on the Receive Connector is not the source of the problem - every server I have implemented has the server FDN on the recieve connector. None of them have been blacklisted.

            As I wrote above, it isn't the FQDN on the Receive Connector at fault.

            Simon.
            --
            Simon Butler
            Exchange MVP

            Blog: http://blog.sembee.co.uk/
            More Exchange Content: http://exchange.sembee.info/
            Exchange Resources List: http://exbpa.com/
            In the UK? Hire me: http://www.sembee.co.uk/

            Sembee is a registered trademark, used here with permission.

            Comment

            Working...
            X