Exchange 2007 SMTP Domains

I"m setting up a test organization with Exchange 2007.  The domain name inside is divind.internal and the public domain is divind.com.  I can connect to the Exchange server with Outlook 2007 no problem and send to anyone else using a divind.internal address.  When I try to send an email out to the Internet, I get the following error:

Microsoft Exchange couldn't deliver the message to this recipient because it didn't recognize you as a valid sender. Please verify that you have the correct sending address configured in your e-mail client and try sending your message again, or provide the following diagnostic text to your system administrator

The following organization rejected your message: imta20.emeryville.ca.mail.comcast.net.

Now, I know that .internal is not routable over the Internet and .com is.  How can I get this annoying error to go away?
sedberg1Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Rick FeeMessaging Engineer - Disaster Recovery EngineerCommented:
Have you setup divind.com as an accepted domain?  


0
supportsCommented:
I guess u can change the SMTP to gmail if u have a gmail account and authorize your gmail account to send out emails
0
Rick FeeMessaging Engineer - Disaster Recovery EngineerCommented:
Exchange Management Console -->  Org Config --> Hub Transport -->  Accepted Domains tab...


0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

sedberg1Author Commented:
EndureKona,

I went into organization Configuration > Hub Transport > Accepted Domains > New Accepted Domain and did add that domain.  Divind.com is the domain that users outside my organization would send to while divind.internal is the name of my domain inside the LAN.  

The problem happens when I send to an outside address like Comcast.

0
sedberg1Author Commented:
You know what I just noticed, I sent to a Gmail account and didn't get the error.  Is there something wrong with my DNS records for divind.com?  
0
Rick FeeMessaging Engineer - Disaster Recovery EngineerCommented:
If your sending out email you want to ensure your have MX records and PTR records porperly setup.   Did you just setup this divind.com accepted domain?   If clock on the Email Address Policies (Exchange Management Console -->  Org Config --> Hub Transport -->  email address policies)  
And add divind.com and set as the primary and make sure it changes all the mailboxes to use divind.com as the primary.   My guess is still when you send its going out as users@divind.local  you want this to be set as com.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
sedberg1Author Commented:
I have an accepted domain for both divind.internal and divind.com.  They are both authoritative.  I did nothing in Email Address Policies but there appears a Default Policy in this list with the lowest priority.  Under Applied, the Default Policy says False.  How would I change the primary to divind.com for all mailboxes?
0
Rick FeeMessaging Engineer - Disaster Recovery EngineerCommented:
Edit the Default Policy under Email Address Policies...the Email Addresses section click Add...select Select accpeted domain for email address click Browse select divind.com...then select Set as Reply...set the schedule to run immeditaely...once done right click on Default Policy and select Apply.
0
sedberg1Author Commented:
Ok, I did that. The emails go out and I don't get an error back from the Exchange server.  However, the emails didn't show up in the destination's inbox.  Tried sending to an external .net, .com, and Gmail account.  Before, the emails were at least going to the Gmail account.  Now they don't.  They're not in the Queue, I checked.
0
sedberg1Author Commented:
Ok, I put something in wrong in the Email Address Policy.  When I added divind.com, there was a %m in front of it.  I edited the divind.com and unchecked the box for Email address local part, and the problem went away.  Can now send/receive externally no problem!  

Thanks for your help!  This Exchange stuff is not so easy.  I'm reading an MS Press book on how to do this, and it's tough.  The examples they give you, I try to apply to my real domain in a test VM.  Not very simple with all the connectors, policies, shell, folders, etc.
0
Rick FeeMessaging Engineer - Disaster Recovery EngineerCommented:
cool glad the issue is resolved...good deal about the book that's the same way I pick this stuff up
0
sedberg1Author Commented:
If anyone's interested about the book, the one I got was VERY helpful in learning Exchange 2007.  In fact, I feel like I can tackle a full Exchange environment now.  The book is a MS Press book titled Configuring Microsoft Exchange Server 2007, ISBN: 978-0-7356-2410-8
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.