Exchange 2003 smtp issue

We recently added our own server (SBS 2003 w/Exchange).  Our domain registrar has added the correct mx record with rDNS entry,however, we are unable to send to aol or comcast and get the following response:
 Could not deliver the message in the time limit specified.  Please retry or contact your administrator.
            <hollychev.local #4.4.7>

dnsstuff reports:
WARNING: One or more of your mailservers is claiming to be a host other than what it really is (the SMTP greeting should be a 3-digit code, followed by a space or a dash, then the host name). If your mailserver sends out E-mail using this domain in its EHLO or HELO.... claims to be non-existent host hollychev.local:
220 hollychev.local Microsoft ESMTP MAIL Service, Version: 6.0.3790.3959 ready at Sat, 21 Jul 2007 09:31:25 -0500

I'm certain the issue has to do with mail.*.com and host *.local, but can't determine what changes I need to make.

Who is Participating?
This is exactly as you guessed Drlannie,

You need to change the SMTP Greeting, and I have provided instructions on doing this here ->

Have you set the masqurade domain to reflect your domain?
You also need to make sure you have set the recipent policey correctly and that DNS between the local server and the internet is working correctly.
drlannieAuthor Commented:
Thanks for your help. I followed your instructions, but continue to get the same failure. I went as far as to restart the server, but my messages to aol and comcast.

In looking at the returned message, it appears that I'm still getting the wrong id:
Content-class: urn:content-classes:message
Date: Mon, 23 Jul 2007 07:06:03 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Message-ID: <48853EF7C3D24446B77B6C98C7A02B3EC7CE@hc1.HollyChev.local>
Thread-Topic: Holly Chevrolet Test message
Thread-Index: AcfNIfultDV9Pjc3T5+zrOc7FovVBg==
From: "Lannie Lancaster" <>
To: <>

Any ideas?
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

drlannieAuthor Commented:
As an afterthought:
When I look at Outlook 2003 on my client, the hc1.hollchev.local shows up in Exchange Server field.

What Outlook uses internally has nothing to do with how the server is seen externally.
Does the name that you have put in the FQDN match the reverse DNS of the server? AOL and other major providers are very picky about who they accept email from.

Forced accept.

EE Admin
drlannieAuthor Commented:
I'm sorry for the delay in responding. This ended up being an issue with AT&T and our previous email host. THANKS!
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.