Hello

I have Exchange 2013 and I can send and receive with no issues but in last 2 weeks I find some domains reject my mails with the below error :

Can not deliver the message you sent. Will not retry.

Sender: <fdgr@bd.comw>

The following addresses had delivery problems

<bgdwed@nbgt.com> : Reply from host.onyxservers.com[72.52.154.132]:
        >>> MAIL FROM:<fdgr@bd.comw> SIZE=19729
        <<< 550 Access denied - Invalid HELO name (See RFC2821 4.1.1.1)

Hello

I have Exchange 2013 and I can send and receive with no issues but in last 2 weeks I find some domains reject my mails with the below error :

Can not deliver the message you sent. Will not retry.

Sender: <fdgr@bd.comw>

The following addresses had delivery problems

<bgdwed@nbgt.com> : Reply from host.onyxservers.com[72.52.154.132]:
        >>> MAIL FROM:<fdgr@bd.comw> SIZE=19729
        <<< 550 Access denied - Invalid HELO name (See RFC2821 4.1.1.1)

try in the send connector with resolve mx records in-stat of working with a smart host.

also try sending a mail from a other domain, to see it they receive your mail. it could be that the receiver has some problems with receiving mails.

it's possible the receiver has this activated  SMTP server requires authentication" checked

Hello

I have Exchange 2013 and I can send and receive with no issues but in last 2 weeks I find some domains reject my mails with the below error :

Can not deliver the message you sent. Will not retry.

Sender: <fdgr@bd.comw>

The following addresses had delivery problems

<bgdwed@nbgt.com> : Reply from host.onyxservers.com[72.52.154.132]:
        >>> MAIL FROM:<fdgr@bd.comw> SIZE=19729
        <<< 550 Access denied - Invalid HELO name (See RFC2821 4.1.1.1)

Hello

I have Exchange 2013 and I can send and receive with no issues but in last 2 weeks I find some domains reject my mails with the below error :

Can not deliver the message you sent. Will not retry.

Sender: <fdgr@bd.comw>

The following addresses had delivery problems

<bgdwed@nbgt.com> : Reply from host.onyxservers.com[72.52.154.132]:
        >>> MAIL FROM:<fdgr@bd.comw> SIZE=19729
        <<< 550 Access denied - Invalid HELO name (See RFC2821 4.1.1.1)

Hi,

According to your question, I understant that cannot send message to some domian with reject message "550 Access denied - Invalid HELO name (See RFC2821 4.1.1.1)". If I misunderstand your concern, please do not hesitate to let me know.

Here's an similar thread about your question, please refer to:
https://social.technet.microsoft.com/Forums/office/en-US/a1edf1aa-f54a-4e16-829b-a99e51003521/550-access-denied-invalid-helo-name-see-rfc2821-4111?forum=exchange2010

Since this issue only occur on individual domain, it might caused by the anti-spam setting for destination domain. You can contact its administrator to confirm.

First, please run Get-SendConnector | FL to check the authentication, TLS and other relevant setting by problematic domain name or IP address.
Second, use Message tracking log to monitor the deliver process so that get detail information for it.

Thanks

Hi,

According to your question, I understant that cannot send message to some domian with reject message "550 Access denied - Invalid HELO name (See RFC2821 4.1.1.1)". If I misunderstand your concern, please do not hesitate to let me know.

Here's an similar thread about your question, please refer to:
https://social.technet.microsoft.com/Forums/office/en-US/a1edf1aa-f54a-4e16-829b-a99e51003521/550-access-denied-invalid-helo-name-see-rfc2821-4111?forum=exchange2010

Since this issue only occur on individual domain, it might caused by the anti-spam setting for destination domain. You can contact its administrator to confirm.

First, please run Get-SendConnector | FL to check the authentication, TLS and other relevant setting by problematic domain name or IP address.
Second, use Message tracking log to monitor the deliver process so that get detail information for it.

There are SMTP test sites out there. Example:

http://mxtoolbox.com/diagnostic.aspx

There are SMTP test sites out there. Example:

http://mxtoolbox.com/diagnostic.aspx

Look in the protocol logs to see the actual conversation your own server(s) have  with the recipient's domain. Since there were interesting side-notes with the FQDN, at least in Exchange Server 2010 (FQDN section in this article), it might be best to looks at resulting conversation, instead of individual settings. Verbose logging should be set against the connector used to send mails to Internet (Get-Sendconnector | ft Name, AddressSpaces, Fqdn, ProtocolLoggingLevel will provide if this is already set). Next the path of the logs can be extracted from all source servers used for that send connector using Get-TransportService <MailboxServer> | fl SendProtocolLogPath. Once inside things should be pretty clear once the EHLO line your own server is sending is identified.

Last and not least - is there only a handful of recipient organizations refusing messages or the majority of them ? If 1-2, then it could be the recipient's systems or the RBL providers (including PTR checks for your sending host) that might be having issues.

There are SMTP test sites out there. Example:

http://mxtoolbox.com/diagnostic.aspx