Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people, just like you, are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
Solved

HELO/EHLO error when sending to comcast addresses

Posted on 2006-07-17
3
725 Views
Last Modified: 2012-08-14
I get an error anytime I (or anyone within my Exchange organization) sends an email to someone with a comcast address including replies.  We can send to all other addresses.  And can send to those addresses using other smtp or email accounts.  This is the error I get:

  *******@comcast.net on 7/17/2006 4:04 PM
            There was a SMTP communication problem with the recipient's email server.  Please contact your system administrator.
            <geek3.Coakley.local #5.5.0 smtp;521-EHLO/HELO from sender 151.200.144.10 does not map to geek3.coakley.local in DNS>

How do I correct this?  I have checked the various blacklist sites, and I cannot find that we have been put on any of them.  I note that the difference in the DNS addresses above is geek3.Coakley.local versus geek3.coakley.local is the letter C in Coakley.  Is it case sensitive?  And if so how can I make this correction?  

Please give descriptive instructions as I am only a novice.  

Thank you for your help.
0
Comment
Question by:aiasslug
  • 2
3 Comments
 
LVL 104

Accepted Solution

by:
Sembee earned 250 total points
ID: 17125629
Your SMTP banner is incorrect and will fail some tests.

Anything ending in .local will fail.

You need to correct your SMTP banner, your reverse DNS and forward DNS.
See my web site here: http://www.amset.info/exchange/dnsconfig.asp

Simon.
0
 

Author Comment

by:aiasslug
ID: 17132969
Do I need to make any changes on the DNS server in my network?  Like the forward lookup zones or reverse lookup zones?  Or do I just need to contact Verizon to verify that our PTR and MX records match?
0
 
LVL 104

Expert Comment

by:Sembee
ID: 17133023
Reverse lookup is set by your ISP, so you will need to contact them.
If your email is being delivered by SMTP then the forward DNS will be fine.

Changes to your internal network DNS are pointless - they will affect the internet.

Simon.
0

Featured Post

PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This process describes the steps required to Import and Export data from and to .pst files using Exchange 2010. We can use these steps to export data from a user to a .pst file, import data back to the same or a different user, or even import data t…
How to resolve IMCEAEX NDRs in Exchange or Exchange Online related to invalid X500 addresses.
how to add IIS SMTP to handle application/Scanner relays into office 365.
This video shows how to quickly and easily add an email signature for all users on Exchange 2016. The resulting signature is applied on a server level by Exchange Online. The email signature template has been downloaded from: www.mail-signatures…

840 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question