Solved

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

Posted on 2016-08-18
9
26 Views
Last Modified: 2016-08-22
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
Comment
Question by:Castlewood
  • 5
  • 4
9 Comments
 
LVL 24

Expert Comment

by:-MAS
ID: 41761282
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
 

Author Comment

by:Castlewood
ID: 41761347
I need to put the newly aqcuired company's domain name (domain2.com) into the Accepted Domain on HQ Exchange, correct?
0
 
LVL 24

Accepted Solution

by:
-MAS earned 500 total points
ID: 41761413
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
 

Author Comment

by:Castlewood
ID: 41761443
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
Too many email signature updates to deal with?

Do you feel like you are taking up all of your time constantly visiting users’ desks to make changes to email signatures? Wish you could manage all signatures from one central location, easily design them and deploy them quickly to users? Well, there is an easy way!

 
LVL 24

Expert Comment

by:-MAS
ID: 41761466
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
 

Author Comment

by:Castlewood
ID: 41761472
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
 

Author Comment

by:Castlewood
ID: 41761636
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
 
LVL 24

Expert Comment

by:-MAS
ID: 41761646
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
 

Author Comment

by:Castlewood
ID: 41761663
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

Find Ransomware Secrets With All-Source Analysis

Ransomware has become a major concern for organizations; its prevalence has grown due to past successes achieved by threat actors. While each ransomware variant is different, we’ve seen some common tactics and trends used among the authors of the malware.

Join & Write a Comment

Suggested Solutions

Title # Comments Views Activity
outlook 15 44
Exchange 2007 export to PST 12 62
MX Backup 4 40
Exchange 2013 Update Issue CU7 to CU13 5 40
We are happy to announce a brand new addition to our line of acclaimed email signature management products – CodeTwo Email Signatures for Office 365.
Exchange server is not supported in any cloud-hosted platform (other than Azure with Azure Premium Storage).
In this video we show how to create an Address List in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Organization >> Ad…
This video discusses moving either the default database or any database to a new volume.

744 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

12 Experts available now in Live!

Get 1:1 Help Now