Emails can not be delivered internally

I recently moved through a migration of changing my organizations email from .com to .org. All email is working from external to internal and email is being accepted to the users new .org email and through recipient policy, still being accepted through the .com email as well. On occassion, and not every time, when a user forwards an email or sends an email internally, they sometimes recieve the error "The message could not be delivered because the recipient's destination email system is unknown or invalid. Please check the address and try again, or contact your system administrator to verify connectivity to the email system of the recipient."


This is sending email internally and I have verified that the GAL is being updated correctly and at 3 times throughout the day. Any other suggestions on what it could be?
dsheltzelAsked:
Who is Participating?
 
SembeeConnect With a Mentor Commented:
Outlook can't generate the message.
But if something has been set on the Outlook client - like a rule to forward email messages out, a delegate - perhaps for an ex-employee things like that, then the message can be generated.

Simon.
0
 
SembeeCommented:
Internal email doesn't use SMTP. The SMTP address on the account shouldn't matter.
Is this a single server, multiple servers?
Which version of Exchange, on which version of Windows?
Are you using a smart host for delivery of email at all?

Simon.
0
 
dsheltzelAuthor Commented:
This is a back end server. I use a front end server sitting in the DMZ for OWA but there is no configuration on it. It is Exchange Server 2003 SP2 running on W2K3. I am not using any kind of samrt host for delivery.
0
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

 
SembeeCommented:
What does message tracking say?

Simon.
0
 
dsheltzelAuthor Commented:
How do I look up the message tracking?
0
 
SembeeCommented:
0
 
dsheltzelAuthor Commented:
Message tracking does not show the bounced message, but only shows the one that went through successfully. It was turned on already.

0
 
SembeeCommented:
Can you find the NDR coming back in?

Simon.
0
 
dsheltzelAuthor Commented:
I could not find it in message tracking, however, the original message had the error 5.1.2. Does this help at all?
0
 
SembeeCommented:
NDR codes on their own are close to useless.
What I am trying to discover is whether the message is being sent outside of the Exchange org somehow. If message tracking doesn't show the generation of the NDR, then it is possible that the NDR is being generated outside of the server.

Simon.
0
 
dsheltzelAuthor Commented:
So it could be possible at the client level? Could Outlook generate this message somehow? The reason I didnt go down this path is because people have also recieved this message from home using OWA on the fornt end server.
0
 
dsheltzelAuthor Commented:
Simon,

You rock dude. Well, hopefully it will not do it again. It has only happened a couple times. I will keep my eye open and see if I can pin it down.

Thanks for the help!
0
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.