Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

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

How to forward emails from Exchange1 to another Exchange2 without creating mailboxes in Exchnage1 ?

We have a newly acquired company with one Exchange 2010 called Exchange2 and the domain say domain2.com. We want their emails coming to our HQ Exchange server firstly and then got forwarded to Exchange2 without creating their user mailbox in HQ Exchange server. Is it possible? How?
0
Castlewood
Asked:
Castlewood
  • 5
  • 4
1 Solution
 
MASTechnical Department HeadCommented:
This expert suggested creating a Gigs project.
Hi Please do as below.

On exchange1 -> EMC -> org config -> Hub transport-> Create a send connector and make it use the IP of Exchange2 as smart host relay.
https://technet.microsoft.com/en-us/library/jj839710(v=exchg.141).aspx

On exchange2 -> EMC -> server config -> hub tranposrt -> create a new receive connector make it accept connections from the IP of Exchange1 and allow relaying on it.

Create Receive connector https://technet.microsoft.com/en-us/library/bb125159(v=exchg.141).aspx

Use this to allow relay.
https://www.experts-exchange.com/articles/2666/Allow-relaying-on-Exchange-2007-Exchange-2010-in-4-easy-steps.html

Thanks
MAS
0
 
CastlewoodAuthor Commented:
I need to put the newly aqcuired company's domain name (domain2.com) into the Accepted Domain on HQ Exchange, correct?
0
 
MASTechnical Department HeadCommented:
I apologize for that missed part.

On exchange1 -> EMC -> org config -> Hub transport-> Send connectors --> Create a send connector and make it use the IP of Exchange2 as smart host relay.
https://technet.microsoft.com/en-us/library/jj839710(v=exchg.141).aspx

On exchange1 -> EMC -> org config -> Hub transport-> Accepted domains-->Create a domain as internal relay.
New-AcceptedDomain -Name "Domain2" -DomainName domain2.com -DomainType InternalRelay

Open in new window



On exchange2 -> EMC -> server config -> hub tranposrt -> create a new receive connector make it accept connections from the IP of Exchange1 and allow relaying on it.

Create Receive connector https://technet.microsoft.com/en-us/library/bb125159(v=exchg.141).aspx

Run this command to allow relaying on the connector created above
Get-ReceiveConnector <NEWCONNECTORNAME> | Add-ADPermission -User "NT AUTHORITY\ANONYMOUS LOGON" -ExtendedRights "ms-Exch-SMTP-Accept-Any-Recipient"

Open in new window

Use this to allow relay.
https://www.experts-exchange.com/articles/2666/Allow-relaying-on-Exchange-2007-Exchange-2010-in-4-easy-steps.html

Thanks
MAS
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
CastlewoodAuthor Commented:
A side question....
In HQ Exchange I've had an existing Send Connector (#1) which is with '*' in Address Space where the '*' I believe means ALL. You now want me to add one more Send Connector (#2) with the Address Space = *.domain2.com. It seems the two address spaces have an overlapping area. So my concern is, would an email intended to domain2.com be handled by the #1 Send Connector instead of the #2 ? In another word, how does an Exchange server determine which Send Connector to go to if the Address Spaces overlap?
0
 
MASTechnical Department HeadCommented:
You will have 2 send connectors in your HQ exchange server.
1 with address space "*" and with cost 2
2 with address space "*.domain2.com" and with cost 1

Thanks
MAS
0
 
CastlewoodAuthor Commented:
I got your idea. The different cost makes it work, just as the "metric" plays in IP routing -- the lower value the higher priority. Currently both connectors are with cost = 1. I'm gonna change it.  
Thanks for help.
0
 
CastlewoodAuthor Commented:
Hi MAS,

Want to verify the necessity of creating a Receive Connector on Exchange2 since
1. Exchange2 is the final destination with Mail boxes so don't need relay. Conversely besides the Send Connector, shall we need to create a new Receive Connector on HQ Exchange to receive and relay domain2.com emails to Exchange1 ?
2. the existing Receive Connector already covers ALL ip addresses (received from a filtering smart host)

What you think?
0
 
MASTechnical Department HeadCommented:
1. Exchange2 is the final destination with Mail boxes so don't need relay. Conversely besides the Send Connector, shall we need to create a new Receive Connector on HQ Exchange to receive and relay domain2.com emails to Exchange1 ?

No need. You can send email directly out from Exchange2 if you have internet on Exchange2.
If you dont have internet you can do the same process vice-versa to send email out through HQ server.

2. the existing Receive Connector already covers ALL ip addresses (received from a filtering smart host).
If both the exchange servers are from different forest you have to create a receive connector to allow relay.

Thanks
MAS
0
 
CastlewoodAuthor Commented:
Sorry I got a typo. The previous question should be:

Shall we need to create a new Receive Connector on HQ Exchange to receive (from a filtering smart host) and then relay the domain2.com emails to Exchange2 via the new Send Connector?

The reason I'm confused is, look, it is the HQ Exchange who relays the inbound mails to Exchange2. Doesn't it need a separate Receive Connector with relay on HQ Exchange ?
0

Featured Post

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.

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