[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 98
  • Last Modified:

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.
0
BMFC
Asked:
BMFC
  • 4
1 Solution
 
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
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
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
 
BMFCAuthor Commented:
Resolved own issue.
0

Featured Post

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

  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now