none
Invalid HELO name (See RFC5321 4.1.1.1)

    Question

  • Dears, 

    i have issue sending mails to some domain, i checked the send connector and found this only,

    my send connector is set

    -----------------------------

    ehlo mails.trimarforwarding.com

    Received: 
    250-mx1.tmdhosting.com Hello mails.trimarforwarding.com [196.202.18.10]
    250-SIZE 10485760
    250-8BITMIME
    250-PRDR
    250 HELP


    Sent: 
    mail from: <test@trimarforwarding.com>

    Received: 
    250 OK

    Sent: 
    rcpt to: <n.rousan@jerasalogistics.com>

    Received: 
    550 Access denied - Invalid HELO name (See RFC5321 4.1.1.1)

    ---------------------------------------------------------------------

    my send connector setting is as below:


    AddressSpaces                : {SMTP:*;1}
    AuthenticationCredential     :
    Comment                      :
    ConnectedDomains             : {}
    ConnectionInactivityTimeOut  : 00:10:00
    DNSRoutingEnabled            : True
    DomainSecureEnabled          : False
    Enabled                      : True
    ErrorPolicies                : Default
    ForceHELO                    : False
    Fqdn                         : mails.trimarforwarding.com
    HomeMTA                      : Microsoft MTA
    HomeMtaServerId              : TFEXMB01
    Identity                     : send
    IgnoreSTARTTLS               : False
    IsScopedConnector            : False
    IsSmtpConnector              : True
    LinkedReceiveConnector       :
    MaxMessageSize               : 10 MB (10,485,760 bytes)
    Name                         : send
    Port                         : 25
    ProtocolLoggingLevel         : Verbose
    RequireOorg                  : False
    RequireTLS                   : False
    SmartHostAuthMechanism       : None
    SmartHosts                   : {}
    SmartHostsString             :
    SmtpMaxMessagesPerConnection : 20
    SourceIPAddress              : 0.0.0.0
    SourceRoutingGroup           : Exchange Routing Group (DWBGZMFD01QNBJR)
    SourceTransportServers       : {TFEXMB01}
    TlsAuthLevel                 :
    TlsDomain                    :
    UseExternalDNSServersEnabled : False

    any help i don't know what is the issue the fqdn is the same as ptr record. 

    Friday, January 27, 2017 11:47 PM

All replies

  • Is mails.trimarforwarding.com the Internet host name of the server?

    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    Celebrating 20 years of providing Exchange peer support!

    Saturday, January 28, 2017 6:08 AM
    Moderator
  • yes it's check the below smtp diag from mxtoolbox

    SMTP Banner Check Reverse DNS does not match SMTP Banner  More Info
    SMTP Transaction Time 8.566 seconds - Not good! on Transaction Time  More Info
    SMTP Reverse DNS Mismatch OK - 196.202.18.10 resolves to mails.trimarforwarding.com
    SMTP Valid Hostname OK - Reverse DNS is a valid Hostname
    SMTP TLS OK - Supports TLS.
    SMTP Connection Time 1.047 seconds - Good on Connection time
    SMTP Open Relay OK - Not an open relay.

    Saturday, January 28, 2017 11:30 PM
  • Everything I see on the sending side looks right.

    How does MXToolbox check your sending banner?  I suspect that it's reporting your receiving banner, so I telnetted to your server and see that your receiving banner (receive connector's FQDN property) is the server name, but that wouldn't impact the sending problem you're reporting.

    You might want to turn up protocol logging on the send connector and see what's being sent.


    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    Celebrating 20 years of providing Exchange peer support!


    Sunday, January 29, 2017 3:05 AM
    Moderator
  • here is the log from send protocol

    2017-01-18T07:47:08.261Z,send,08D43D0E5B1CCB95,0,,103.254.154.3:25,*,,attempting to connect
    2017-01-18T07:47:08.276Z,send,08D43D0E5B1CCB95,1,10.1.1.7:10638,103.254.154.3:25,+,,
    2017-01-18T07:47:09.431Z,send,08D43D0E5B1CCB95,2,10.1.1.7:10638,103.254.154.3:25,<,"220 mx25.antispamcloud.com ESMTP Exim 4.86-111125 Wed, 18 Jan 2017 08:43:08 +0100",
    2017-01-18T07:47:09.431Z,send,08D43D0E5B1CCB95,3,10.1.1.7:10638,103.254.154.3:25,>,EHLO mails.trimarforwarding.com,
    2017-01-18T07:47:09.665Z,send,08D43D0E5B1CCB95,4,10.1.1.7:10638,103.254.154.3:25,<,250-mx25.antispamcloud.com Hello mails.trimarforwarding.com [196.202.18.10],
    2017-01-18T07:47:09.665Z,send,08D43D0E5B1CCB95,5,10.1.1.7:10638,103.254.154.3:25,<,250-SIZE 10485760,
    2017-01-18T07:47:09.665Z,send,08D43D0E5B1CCB95,6,10.1.1.7:10638,103.254.154.3:25,<,250-8BITMIME,
    2017-01-18T07:47:09.665Z,send,08D43D0E5B1CCB95,7,10.1.1.7:10638,103.254.154.3:25,<,250-PRDR,
    2017-01-18T07:47:09.665Z,send,08D43D0E5B1CCB95,8,10.1.1.7:10638,103.254.154.3:25,<,250 HELP,
    2017-01-18T07:47:09.665Z,send,08D43D0E5B1CCB95,9,10.1.1.7:10638,103.254.154.3:25,*,97234,sending message
    2017-01-18T07:47:09.665Z,send,08D43D0E5B1CCB95,10,10.1.1.7:10638,103.254.154.3:25,>,MAIL FROM:<xxxxx@trimarforwarding.com> SIZE=1346944,
    2017-01-18T07:47:09.930Z,send,08D43D0E5B1CCB95,11,10.1.1.7:10638,103.254.154.3:25,<,250 OK,
    2017-01-18T07:47:09.930Z,send,08D43D0E5B1CCB95,12,10.1.1.7:10638,103.254.154.3:25,>,RCPT TO:<xxxxx@elsalampapermill.com>,
    2017-01-18T07:47:10.835Z,send,08D43D0E5B1CCB95,13,10.1.1.7:10638,103.254.154.3:25,<,550 Access denied - Invalid HELO name (See RFC5321 4.1.1.1),
    2017-01-18T07:47:10.991Z,send,08D43D0E5B1CCB95,14,10.1.1.7:10638,103.254.154.3:25,>,QUIT,

    Tuesday, January 31, 2017 8:38 AM
  • Are you sure that you're sending through the same IP address as you're using for inbound mail?

    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    Celebrating 20 years of providing Exchange peer support!

    Tuesday, January 31, 2017 10:55 PM
    Moderator
  • yes i am sure it's the same IP, i have one internet line with only 1 external IP

    • Marked as answer by douha-it Wednesday, February 1, 2017 9:56 PM
    • Unmarked as answer by douha-it Wednesday, February 1, 2017 10:15 PM
    Wednesday, February 1, 2017 5:54 PM
  • Hi.

    Exchange 2013 – Configure Send Connectors.

    Get-SendSonnector |fl forcehelo

    Maybe

    Set-SendConnector -ForceHELO $true


    MCITP, MCSE. Regards, Oleg

    Wednesday, February 1, 2017 6:08 PM
  • the same

    [PS] C:\Windows\system32>Get-SendConnector send | fl


    AddressSpaces                : {SMTP:*;1}
    AuthenticationCredential     :
    Comment                      :
    ConnectedDomains             : {}
    ConnectionInactivityTimeOut  : 00:10:00
    DNSRoutingEnabled            : True
    DomainSecureEnabled          : False
    Enabled                      : True
    ErrorPolicies                : Default
    ForceHELO                    : True
    Fqdn                         : mails.trimarforwarding.com
    HomeMTA                      : Microsoft MTA
    HomeMtaServerId              : TFEXMB01
    Identity                     : send
    IgnoreSTARTTLS               : False
    IsScopedConnector            : False
    IsSmtpConnector              : True
    LinkedReceiveConnector       :
    MaxMessageSize               : 10 MB (10,485,760 bytes)
    Name                         : send
    Port                         : 25
    ProtocolLoggingLevel         : Verbose
    RequireOorg                  : False
    RequireTLS                   : False
    SmartHostAuthMechanism       : None
    SmartHosts                   : {}
    SmartHostsString             :
    SmtpMaxMessagesPerConnection : 20
    SourceIPAddress              : 0.0.0.0
    SourceRoutingGroup           : Exchange Routing Group (DWBGZMFD01QNBJR)
    SourceTransportServers       : {TFEXMB01}
    TlsAuthLevel                 :
    TlsDomain                    :
    UseExternalDNSServersEnabled : False

    here is the diagnostic report:

    n.rousan@jerasalogistics.com
    mx1.tmdhosting.com #550 Access denied - Invalid HELO name (See RFC5321 4.1.1.1) ##
    Original message headers:
    Received: from TFEXMB01.trimar.local ([::1]) by tfexmb01.trimar.local ([::1])
     with mapi id 14.03.0123.003; Thu, 2 Feb 2017 00:40:34 +0200
    From: business development <business.development@trimarforwarding.com>
    To: "n.rousan@jerasalogistics.com" <n.rousan@jerasalogistics.com>
    Subject: RE: test
    Thread-Topic: test
    Thread-Index: AdJwpufc/xGF0tQVQsaLhdV3Dte0RQMM7VSAAABaohc=
    Date: Wed, 1 Feb 2017 22:40:32 +0000
    Message-ID: <2B406A1A945EEA40A00D6630C8693F70288E35C2@tfexmb01.trimar.local>
    References: <2B406A1A945EEA40A00D6630C8693F70288E1325@tfexmb01.trimar.local>,<2B406A1A945EEA40A00D6630C8693F70288E2DA7@tfexmb01.trimar.local>
    In-Reply-To: <2B406A1A945EEA40A00D6630C8693F70288E2DA7@tfexmb01.trimar.local>
    Accept-Language: en-US
    Content-Language: en-US
    X-MS-Has-Attach:
    X-MS-TNEF-Correlator:
    x-originating-ip: [156.194.54.192]
    Content-Type: multipart/alternative;
         boundary="_000_2B406A1A945EEA40A00D6630C8693F70288E35C2tfexmb01trimarl_"
    MIME-Version: 1.0

    i don't know if the issue may be because of ipv6 loop back i disabled it using the reg key but it still appear at the diagnostic report.

    Wednesday, February 1, 2017 11:05 PM
  • Some anti spam solutions do a forward lookup on your mx record .

    Maybe it failing there.

    This should be the FQDN you are using in your MX record.

    mails.trimarforwarding.com

    Not

    220 tfexmb01.trimar.local Microsoft ESMTP MAIL Service ready at Thu, 2 Feb 2017

    That is set on the receive connector used for receiving internet mail. That should be fixed regardless.


    Blog:    Twitter:   

    Wednesday, February 1, 2017 11:35 PM
  • Ok.

    I run test smtp connection

    smtp:196.202.18.10   Monitor This  

    QuickWatch smtp

    DNS Warning  

    220 tfexmb01.trimar.local Microsoft ESMTP MAIL Service ready at Thu, 2 Feb 2017 15:42:26 +0200

    Test Result
    SMTP Banner Check Reverse DNS does not match SMTP Banner  More Info
    SMTP Connection Time 13.688 seconds - Not good! on Connection time  More Info
    SMTP Transaction Time 21.689 seconds - Not good! on Transaction Time  More Info
    SMTP Reverse DNS Mismatch OK - 196.202.18.10 resolves to mails.trimarforwarding.com
    SMTP Valid Hostname OK - Reverse DNS is a valid Hostname
    SMTP TLS OK - Supports TLS.
    SMTP Open Relay OK - Not an open relay.
    Session Transcript:
    Connecting to 196.202.18.10

    220 tfexmb01.trimar.local Microsoft ESMTP MAIL Service ready at Thu, 2 Feb 2017 15:42:26 +0200 [13438 ms]
    EHLO PWS3.mxtoolbox.com
    250-tfexmb01.trimar.local Hello [64.20.227.134]
    250-SIZE
    250-PIPELINING
    250-DSN
    250-ENHANCEDSTATUSCODES
    250-STARTTLS
    250-X-ANONYMOUSTLS
    250-AUTH NTLM
    250-X-EXPS GSSAPI NTLM
    250-8BITMIME
    250-BINARYMIME
    250-CHUNKING
    250-XEXCH50
    250-XRDST
    250 XSHADOW [891 ms]
    MAIL FROM:<supertool@mxtoolbox.com>
    250 2.1.0 Sender OK [781 ms]
    RCPT TO:<test@example.com>
    550 5.7.1 Unable to relay [5938 ms]

    PWS3v2 23111ms

    I see baner 220 tfexmb01.trimar.local on receive connector.

    I think:

    1. Check FQDN Send Connector, must be have - mails.trimarforwarding.com.

    2. Check FQND Receive Connector, must be have - mails.trimarforwarding.com

    I recomend make Receive connector for Internet and don't use default Receive connector.

    You can make banner How to set the Exchange 2013 Mail Header/Banner for SMTP 


    MCITP, MCSE. Regards, Oleg

    Thursday, February 2, 2017 1:46 PM
  • i have issue with sending mails not receiving mail.

    Thursday, February 2, 2017 5:49 PM
  • i have issue with sending mails not receiving mail.


    Yep, but like I said, some anti spam solutions do a forward lookup and check the mx record. Regardless, you should fix that on the internet receive connector. I assume you have one just for internet mail.

    Blog:    Twitter:   

    Thursday, February 2, 2017 5:59 PM
  • i created new smtp recieve connector as i cann't change the fqdn on the default one, but still have the same issue
    Sunday, February 5, 2017 12:57 PM
  • I telnetted into your mail server and it is presenting mails.trimarforwarding.com as the FQDN.  You might want to contact the postmasters of some of the domains you're having problems sending to and maybe they can give you some clues as to what's wrong.

    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    Celebrating 20 years of providing Exchange peer support!

    Monday, February 6, 2017 5:36 AM
    Moderator
  • ok i have have issue with send connector

    here is my send connector setting:

    [PS] C:\Windows\system32>Get-SendConnector | fl
    --------------------------------------------------------------------

    AddressSpaces                : {SMTP:*;1}
    AuthenticationCredential     :
    Comment                      :
    ConnectedDomains             : {}
    ConnectionInactivityTimeOut  : 00:10:00
    DNSRoutingEnabled            : True
    DomainSecureEnabled          : True
    Enabled                      : True
    ErrorPolicies                : Default
    ForceHELO                    : False
    Fqdn                         : mails.trimarforwarding.com
    HomeMTA                      : Microsoft MTA
    HomeMtaServerId              : TFEXMB01
    Identity                     : internet
    IgnoreSTARTTLS               : False
    IsScopedConnector            : False
    IsSmtpConnector              : True
    LinkedReceiveConnector       :
    MaxMessageSize               : 10 MB (10,485,760 bytes)
    Name                         : internet
    Port                         : 25
    ProtocolLoggingLevel         : Verbose
    RequireOorg                  : False
    RequireTLS                   : False
    SmartHostAuthMechanism       : None
    SmartHosts                   : {}
    SmartHostsString             :
    SmtpMaxMessagesPerConnection : 20
    SourceIPAddress              : 0.0.0.0
    SourceRoutingGroup           : Exchange Routing Group (DWBGZMFD01QNBJR)
    SourceTransportServers       : {TFEXMB01}
    TlsAuthLevel                 :
    TlsDomain                    :
    UseExternalDNSServersEnabled : False

    --------------------------------------------------------------------

    i tried to send test email to dkimvalidator to check the greeting smtp but some thing is incorrect

    here is the log from dkimvalidator

    --------------------------------------------------------------------

    Received: from [196.202.18.10] (unknown [196.202.18.10]) by relay-1.us-west-2.relay-prod (Postfix) with ESMTP id B4B83E02A1 for <HiakFBjpYb39rD@dkimvalidator.com>; Sat, 18 Feb 2017 11:04:11 +0000 (UTC) Received: from TFEXMB01.trimar.local ([::1]) by tfexmb01.trimar.local ([::1]) with mapi id 14.03.0339.000; Sat, 18 Feb 2017 13:09:12 +0200 From: business development <business.development@trimarforwarding.com> To: "HiakFBjpYb39rD@dkimvalidator.com" <HiakFBjpYb39rD@dkimvalidator.com>

    --------------------------------------------------------------------

    my ip appear as unknown however my send connector setting is configured with fqdn

    here is the log from smtp send connector:

    --------------------------------------------------------------------

    2017-02-18T11:09:13.035Z,internet,08D457E7ACBC1353,0,,52.35.209.90:25,*,,attempting to connect
    2017-02-18T11:09:13.066Z,internet,08D457E7ACBC1353,1,10.1.1.7:57891,52.35.209.90:25,+,,
    2017-02-18T11:09:13.565Z,internet,08D457E7ACBC1353,2,10.1.1.7:57891,52.35.209.90:25,<,220 smtp.mandrillapp.com ESMTP,
    2017-02-18T11:09:13.565Z,internet,08D457E7ACBC1353,3,10.1.1.7:57891,52.35.209.90:25,>,EHLO mails.trimarforwarding.com,
    2017-02-18T11:09:13.799Z,internet,08D457E7ACBC1353,4,10.1.1.7:57891,52.35.209.90:25,<,250-relay-1.us-west-2.relay-prod,
    2017-02-18T11:09:13.799Z,internet,08D457E7ACBC1353,5,10.1.1.7:57891,52.35.209.90:25,<,250-SIZE 10485760,
    2017-02-18T11:09:13.799Z,internet,08D457E7ACBC1353,6,10.1.1.7:57891,52.35.209.90:25,<,250-AUTH PLAIN LOGIN,
    2017-02-18T11:09:13.799Z,internet,08D457E7ACBC1353,7,10.1.1.7:57891,52.35.209.90:25,<,250-ENHANCEDSTATUSCODES,
    2017-02-18T11:09:13.799Z,internet,08D457E7ACBC1353,8,10.1.1.7:57891,52.35.209.90:25,<,250 8BITMIME,
    2017-02-18T11:09:13.799Z,internet,08D457E7ACBC1353,9,10.1.1.7:57891,52.35.209.90:25,*,107677,sending message
    2017-02-18T11:09:13.799Z,internet,08D457E7ACBC1353,10,10.1.1.7:57891,52.35.209.90:25,>,MAIL FROM:<business.development@trimarforwarding.com> SIZE=4389,
    2017-02-18T11:09:14.049Z,internet,08D457E7ACBC1353,11,10.1.1.7:57891,52.35.209.90:25,<,250 2.1.0 Ok,
    2017-02-18T11:09:14.049Z,internet,08D457E7ACBC1353,12,10.1.1.7:57891,52.35.209.90:25,>,RCPT TO:<HiakFBjpYb39rD@dkimvalidator.com>,
    2017-02-18T11:09:14.361Z,internet,08D457E7ACBC1353,13,10.1.1.7:57891,52.35.209.90:25,<,250 2.1.5 Ok,
    2017-02-18T11:09:14.361Z,internet,08D457E7ACBC1353,14,10.1.1.7:57891,52.35.209.90:25,>,DATA,
    2017-02-18T11:09:14.377Z,internet,08D457E7ACBC1353,15,10.1.1.7:57891,52.35.209.90:25,<,354 end data with <CR><LF>.<CR><LF>,
    2017-02-18T11:09:15.219Z,internet,08D457E7ACBC1353,16,10.1.1.7:57891,52.35.209.90:25,<,250 2.0.0 Ok: queued as B4B83E02A1,
    2017-02-18T11:09:15.219Z,internet,08D457E7ACBC1353,17,10.1.1.7:57891,52.35.209.90:25,>,QUIT,

    --------------------------------------------------------------------

    also i had contacted with some partner to check the error from his side he send me this pic

    here is the log from the smtp send connector log

    -----------------------------------------------------------------------------

    2017-02-14T09:50:46.869Z,send,08D4547DABE33292,0,,184.154.208.34:25,*,,attempting to connect
    2017-02-14T09:50:46.869Z,send,08D4547DABE33290,3,10.1.1.7:32006,69.175.69.90:25,>,QUIT,
    2017-02-14T09:50:46.869Z,send,08D4547DABE33290,4,10.1.1.7:32006,69.175.69.90:25,-,,Remote
    2017-02-14T09:50:49.895Z,send,08D4547DABE33292,1,10.1.1.7:32007,184.154.208.34:25,+,,
    2017-02-14T09:50:52.594Z,send,08D4547DABE33292,2,10.1.1.7:32007,184.154.208.34:25,<,"220 se6.mailspamprotection.com ESMTP Exim 4.86-112294 Tue, 14 Feb 2017 03:45:53 -0600",
    2017-02-14T09:50:52.594Z,send,08D4547DABE33292,3,10.1.1.7:32007,184.154.208.34:25,>,EHLO mails.trimarforwarding.com,
    2017-02-14T09:50:52.781Z,send,08D4547DABE33292,4,10.1.1.7:32007,184.154.208.34:25,<,250-se6.mailspamprotection.com Hello mails.trimarforwarding.com [196.202.18.10],
    2017-02-14T09:50:52.781Z,send,08D4547DABE33292,5,10.1.1.7:32007,184.154.208.34:25,<,250-SIZE 10485760,
    2017-02-14T09:50:52.781Z,send,08D4547DABE33292,6,10.1.1.7:32007,184.154.208.34:25,<,250-8BITMIME,
    2017-02-14T09:50:52.781Z,send,08D4547DABE33292,7,10.1.1.7:32007,184.154.208.34:25,<,250-PRDR,
    2017-02-14T09:50:52.781Z,send,08D4547DABE33292,8,10.1.1.7:32007,184.154.208.34:25,<,250 HELP,
    2017-02-14T09:50:52.781Z,send,08D4547DABE33292,9,10.1.1.7:32007,184.154.208.34:25,*,106698,sending message
    2017-02-14T09:50:52.781Z,send,08D4547DABE33292,10,10.1.1.7:32007,184.154.208.34:25,>,MAIL FROM:<mohamed.amin@trimarforwarding.com> SIZE=26265,
    2017-02-14T09:50:52.969Z,send,08D4547DABE33292,11,10.1.1.7:32007,184.154.208.34:25,<,250 OK,
    2017-02-14T09:50:52.969Z,send,08D4547DABE33292,12,10.1.1.7:32007,184.154.208.34:25,>,RCPT TO:<omar@eicoabrasivi.com>,
    2017-02-14T09:50:53.296Z,send,08D4547DABE33292,13,10.1.1.7:32007,184.154.208.34:25,<,550 Access denied - Invalid HELO name (See RFC5321 4.1.1.1),
    2017-02-14T09:50:53.327Z,send,08D4547DABE33292,14,10.1.1.7:32007,184.154.208.34:25,>,QUIT,
    2017-02-14T09:50:53.359Z,send,08D4547DABE33292,15,10.1.1.7:32007,184.154.208.34:25,-,,Remote

    --------------------------------------------------------------------------

    i deleted the smtp connector restart the transport service and create it again from begining but the same

    force ehlo on the smtp connector did not work.

    Saturday, February 18, 2017 11:16 AM