cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
14253
Views
5
Helpful
3
Replies

This message has been blocked because the HELO/EHLO domain is invalid

Hi friends,

 

 We are using cisco ironport c170. Today we cannot send email for particular email id(domain). the error msg as below,

Diagnostic information for administrators:

Generating server: sgm.svc.com.sg

abc@anson.com.sg

[182.**.**.51] #<[182.**.**.51] #5.0.0 smtp; 5.1.0 - Unknown address error 554-'5.7.1 [SPAM] This message

has been blocked because the HELO/EHLO domain is invalid.' (delivery attempts: 0)> #SMTP#

Original message headers:

X-IronPort-AV: E=Sophos;i="4.97,682,1389715200";

d="scan'208,217";a="3362301"

Received: from abcct01.abc.com ([10.**.**.33]) by

sgm.svc.com.sg with ESMTP/TLS/AES128-SHA; 19 Mar 2014 11:17:45 +0800

Received: from abcMB01.abc.com ([fe80::99bb:22a0:nnaa:25cc]) by

abcCT01.abc.com ([::1]) with mapi id 14.03.0123.003; Wed, 19 Mar

2014 11:18:13 +0800

From: "test" <test@abc.com>

To: "abc@anson.com.sg" <abc@anson.com.sg>

Subject: Testing Email

Thread-Topic: Testing Email

Thread-Index: Ac9DIdjTsP9HUS2QTF6cZp6PKztE8g==

Date: Wed, 19 Mar 2014 03:18:12 +0000

Message-ID: <1329D1768D6FBE4A90657F034B26A7E217D7ADD5@abcMB01.abc.com>

Accept-Language: en-US

Content-Language: en-US

X-MS-Has-Attach:

X-MS-TNEF-Correlator:

x-originating-ip: [10.**.**.210]

Content-Type: multipart/alternative;

boundary="_000_1329D1768D6FBE4A90657F034B26A7E217D7ADD5abcMB01_"

MIME-Version: 1.0

 

Thank you.

1 Accepted Solution

Accepted Solutions

Robert Sherwin
Cisco Employee
Cisco Employee

The HELO/EHLO domain that your Cisco IronPort Email Security Appliance (ESA) uses is based on the hostname you configure for your delivery interface under Network -> IP Interfaces.  Please ensure that a valid hostname is configured.  This hostname should match the rDNS records for the public IP address used by your ESA.

Once addressed - you should be able to take the domain in question, and attempt to telnet port 25, and attempt the standard SMTP testing...

$ telnet mail.test.com 25
Trying XYZ.XY.124.XX...
Connected to mail.test.com.
Escape character is '^]'.
220 mail.test.com ESMTP
helo foo.com
250 mail.test.com
mail from: test@test.com
250 sender <test@test.com> ok
rcpt to: robsherw@cisco.com
250 recipient <robsherw@cisco.com> ok
data
354 go ahead
Subject: Test
TESTING
.
250 ok:  Message 8102 accepted

 

 

I hope this helps!

-Robert

 

(*If you have received the answer to your original question, and found this helpful/correct - please mark the question as answered, and be sure to leave a rating to reflect!)

View solution in original post

3 Replies 3

Robert Sherwin
Cisco Employee
Cisco Employee

The HELO/EHLO domain that your Cisco IronPort Email Security Appliance (ESA) uses is based on the hostname you configure for your delivery interface under Network -> IP Interfaces.  Please ensure that a valid hostname is configured.  This hostname should match the rDNS records for the public IP address used by your ESA.

Once addressed - you should be able to take the domain in question, and attempt to telnet port 25, and attempt the standard SMTP testing...

$ telnet mail.test.com 25
Trying XYZ.XY.124.XX...
Connected to mail.test.com.
Escape character is '^]'.
220 mail.test.com ESMTP
helo foo.com
250 mail.test.com
mail from: test@test.com
250 sender <test@test.com> ok
rcpt to: robsherw@cisco.com
250 recipient <robsherw@cisco.com> ok
data
354 go ahead
Subject: Test
TESTING
.
250 ok:  Message 8102 accepted

 

 

I hope this helps!

-Robert

 

(*If you have received the answer to your original question, and found this helpful/correct - please mark the question as answered, and be sure to leave a rating to reflect!)

Hi robsherw,

      Sorry for late reply. After changed the hostname name, which is similar to rDNS record we are able to send the e-mail but can't receive from the other end.

 

220 mail.abc.com ESMTP

helo foo.com

250 mail.abc.com

mail from:test@abc.com

250 sender <test@abc.com> ok

rcpt to:sasi@test.com.sg

550 #5.1.0 Address rejected.

If you are seeing a "550 #5.1.0 Address rejected" - that is the delivery end... either they are not accepting mail for the domain, or the user does not exist.  You would need to find out from the delivery domain end what is occurring.

You can also try to verify that email address, and assure it is there:

http://verify-email.org

I get the same when testing w/ a bad address against my local appliance:

Escape character is '^]'.
220 myesa.local ESMTP
helo foo.com
250 myesa.local
mail from: test@test.com
250 sender <test@test.com> ok
rcpt to: joe@mama.com
550 #5.1.0 Address rejected.

-Robert

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: