Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.
One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.
Course Of The Month
7 days, 8 hours left to enrollBecome a Premium Member and unlock a new, free course in leading technologies each month.
Solved
Host multiple smtp address space in Exchange
Posted on 2006-07-18
One forest One domain;AD2003 Native;EX2003;
Currently we are using on stmp address for this environment.
Since our company will separate to some subsidiary and we determined to manage each organization with OU.
We have to assign separate smtp email address for each subsidiaries.
We will keep current smtp address for a while to recieve email from customer who don't know our email address change.
We are planning to assign smtp address as follows,
@sub1.company.com
@sub2.company.com
@sub3.....
but one of subsidiary has to use,
@separate.com
Looks hosting and recieving multiple smtp name space is not a big problem but I'm worried about "sending". I know on ADUC, we can set which smtp address should be primary, but we are going to manage AD with OU. Is it possible to assign primary smtp address based on OU?
Or are there any concern about this operation?
Currently we are using on stmp address for this environment.
Since our company will separate to some subsidiary and we determined to manage each organization with OU.
We have to assign separate smtp email address for each subsidiaries.
We will keep current smtp address for a while to recieve email from customer who don't know our email address change.
We are planning to assign smtp address as follows,
@sub1.company.com
@sub2.company.com
@sub3.....
but one of subsidiary has to use,
@separate.com
Looks hosting and recieving multiple smtp name space is not a big problem but I'm worried about "sending". I know on ADUC, we can set which smtp address should be primary, but we are going to manage AD with OU. Is it possible to assign primary smtp address based on OU?
Or are there any concern about this operation?
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
2 Comments
Hi,
Do you mean that you want some users to have certain e-mail addresses using one domain and other to have e-mail addresses using different domains? I think you should be able to do what you are after by using LDAP filters on the recipient policies.
See this article is has some info and steps for LDAP filters on recipient policies.
http://searchexchange.techtarget.com/originalContent/0,289142,sid43_gci1119797,00.html
Do you mean that you want some users to have certain e-mail addresses using one domain and other to have e-mail addresses using different domains? I think you should be able to do what you are after by using LDAP filters on the recipient policies.
See this article is has some info and steps for LDAP filters on recipient policies.
http://searchexchange.techtarget.com/originalContent/0,289142,sid43_gci1119797,00.html
You need to provide some detailed information here for a helpful response.
Please answer the following questions and I should be able to help.
Are there multiple public MX records for any or all domains? ( http://checkdns.net ) What I am asking about is wether or not you will be using authoritative and non-authoritatve e-mail domains.
How many domains are you talking about?
The seperating by OU is not bad maybe seperating by AD domain as well. This well ease the overall admin task and add alittle organization but will help with creating the recipient policies necessary and if you follow this make sure and run domainprep in each domain.
<<<We have to assign separate smtp email address for each subsidiaries.>>>>>>>>>
Make either AD domains or OUs with logical names semi descriptive like HQ, Dallas, Austin etc.... If you have a HQ than I would leave them with the "@separate.com" and then flow all incoming mail through a single gateway or 2 if possible. You can leave all users with @separate.com or current address just remeber that the reply to address for each user is the Primary SMTP address as defined in the recipient policy responsible for stamping that set of users wether by domain OU etc... and all mail as long as you don't remove their @seperate.com address will still be able receive mail to that address but if not their ptmiary address it won't be replied to or even seen by receiving party on outgoing mail. Hope that made sense.
It sounds likeyou are on the right track mostly
Or are there any concern about this operation? See links below
I would look at these 3 MS knowledge base articles if you are sharing a namespace ifnot then 1st 2 articles are aaste of time. Also make sure andhave a Public MX record for each new address you need to receive for from anyone outside your Exchange Org.
Sharing SMTP address spaces in Exchange 2000 Server and Exchange Server 2003
( http://support.microsoft.com/kb/321721/en-us )
Authoritative and nonauthoritative domains in Exchange 2000 Server and in Exchange Server 2003
( http://support.microsoft.com/kb/823158/en-us )
HOW TO: Configure Recipient Policies in Exchange
( http://support.microsoft.com/kb/249299/en-us )
Please answer the following questions and I should be able to help.
Are there multiple public MX records for any or all domains? ( http://checkdns.net ) What I am asking about is wether or not you will be using authoritative and non-authoritatve e-mail domains.
How many domains are you talking about?
The seperating by OU is not bad maybe seperating by AD domain as well. This well ease the overall admin task and add alittle organization but will help with creating the recipient policies necessary and if you follow this make sure and run domainprep in each domain.
<<<We have to assign separate smtp email address for each subsidiaries.>>>>>>>>>
Make either AD domains or OUs with logical names semi descriptive like HQ, Dallas, Austin etc.... If you have a HQ than I would leave them with the "@separate.com" and then flow all incoming mail through a single gateway or 2 if possible. You can leave all users with @separate.com or current address just remeber that the reply to address for each user is the Primary SMTP address as defined in the recipient policy responsible for stamping that set of users wether by domain OU etc... and all mail as long as you don't remove their @seperate.com address will still be able receive mail to that address but if not their ptmiary address it won't be replied to or even seen by receiving party on outgoing mail. Hope that made sense.
It sounds likeyou are on the right track mostly
Or are there any concern about this operation? See links below
I would look at these 3 MS knowledge base articles if you are sharing a namespace ifnot then 1st 2 articles are aaste of time. Also make sure andhave a Public MX record for each new address you need to receive for from anyone outside your Exchange Org.
Sharing SMTP address spaces in Exchange 2000 Server and Exchange Server 2003
( http://support.microsoft.com/kb/321721/en-us )
Authoritative and nonauthoritative domains in Exchange 2000 Server and in Exchange Server 2003
( http://support.microsoft.com/kb/823158/en-us )
HOW TO: Configure Recipient Policies in Exchange
( http://support.microsoft.com/kb/249299/en-us )
Featured Post
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
Suggested Solutions
Utilizing an array to gracefully append to a list of EmailAddresses
This article aims to explain the working of CircularLogArchiver. This tool was designed to solve the buildup of log file in cases where systems do not support circular logging or where circular logging is not enabled
To show how to generate a certificate request 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 Servers >> Certificates…
how to add IIS SMTP to handle application/Scanner relays into office 365.
Suggested Courses
Course of the Month7 days, 8 hours left to enroll
737 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.