Exchange 2013 sp1 internal email flow

We recently migrated our Exchange 2007 to Exchange 2013 sp1.  Since then we've noticed something.

It appears all is flowing to the outside and coming back in.  How do I configure Exchange 2013 to ensure if I'm sending an internal email, it stays inside our environment and not hitting public DNS then coming back in?  Because of this internal only email boxes are not working anymore.
BMFCAsked:
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.

Rajitha ChimmaniCommented:
You must add your internal email domain as authoritative in the Accepted domains. Once added, all emails addressed to internal users will be tried for delivery within Exchange organization
0
R--RCommented:
All the mailboxes are located in Exchange 2013? Are both the exchange servers on different sties?
0
BMFCAuthor Commented:
The Exchange 2007 server has been taken offline.  All mailboxes have been moved to Exchange 2013.

On the "accepted domains" tab in EAC, I see one line that has our domain listed as "Authoritative".  We initially noticed this issue because group email boxes are set to receive from only internal email addresses, so they stopped working.  Actually, if I send an email from my Outlook client to a group email address, it works.  If we try to send an email from a server via a monitoring process or something else, it doesn't work.  If I allow these group email boxes to receive from external, they work.

Not sure if this is related, but I do see an error in the log when trying to send from one of our servers to an external email address, (gmail.com) account.

Mailbox unavailable. The server response was: 5.7.1 Unable to relay

Obviously, something isn't configured correctly.
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.

BMFCAuthor Commented:
Something else i just noticed.  By default, Exchange 2013 creates a FrontEndTransport role receive connector that is listening on port 25.  I came and added a HubTransport role for routing email from servers, etc. also on port 25.  I'm assuming this isn't allowed.

What is the recommended way to allow Exchange to relay messages from other IPs?
0
BMFCAuthor Commented:
Resolved. Deleted hubtransport connector listening on port 25.  Modified FrontEnd connector listening on port 25.
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
BMFCAuthor Commented:
Resolved own issue.
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.