Solved

HELO/EHLO error when sending to comcast addresses

Posted on 2006-07-17
3
729 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
[X]
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
  • 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

Backup Solution for AWS

Read about how CloudBerry Backup fully integrates your backups with Amazon S3 and Amazon Glacier to provide military-grade encryption and dramatically cut storage costs on any platform.

Question has a verified solution.

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

Lotus Notes – formerly IBM Notes – is an email client application, while IBM Domino (earlier Lotus Domino) is an email server. The client possesses a set of features that are even more advanced as compared to that of Outlook. Likewise, IBM Domino is…
In-place Upgrading Dirsync to Azure AD Connect
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…
A short tutorial showing how to set up an email signature in Outlook on the Web (previously known as OWA). For free email signatures designs, visit https://www.mail-signatures.com/articles/signature-templates/?sts=6651 If you want to manage em…

730 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