|
exchange
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Routing Groups?Here's the example of my question: This is a retail store chain with a corporate headquarters in one building and remote stores throughout a local market. The IT department wants users in the corporate building to be able to email any users in the stores whilst limiting the stores ability to email corporate users. Most likely they will want the store mgr to be able to reply to whomever emails from corporate and then limit the address book of the store user to only those corp users that is needed. The corp uses Exchange 2003 and I believe they only have one server at corporate for the time being. I believe the corp is considering putting an Exchange Srvr at the remote sites but would this be neccessary? The idea is to not have to do so much administration on the server side if this can be done by installing a separate server at the sites and use Routing Groups and just limiting the users ability to see the Global Address list. Or, maybe I have it all wrong and Routing Groups can not be used for this? Any suggestions or comments, ideas welcome. This is my first time on this list - please, be gentle :) Thank you Kd On Sat, 27 May 2006 18:59:18 -0400, Kd <con***@comcast.net> wrote:
Show quote >Hi group, Well, Routing Groups aren't what you need here and if it was simply a>Here's the example of my question: >This is a retail store chain with a corporate headquarters in one >building and remote stores throughout a local market. The IT department >wants users in the corporate building to be able to email any users in >the stores whilst limiting the stores ability to email corporate users. > >Most likely they will want the store mgr to be able to reply to whomever >emails from corporate and then limit the address book of the store user >to only those corp users that is needed. > >The corp uses Exchange 2003 and I believe they only have one server at >corporate for the time being. I believe the corp is considering putting >an Exchange Srvr at the remote sites but would this be neccessary? The >idea is to not have to do so much administration on the server side if >this can be done by installing a separate server at the sites and use >Routing Groups and just limiting the users ability to see the Global >Address list. Or, maybe I have it all wrong and Routing Groups can not >be used for this? > >Any suggestions or comments, ideas welcome. > >This is my first time on this list - please, be gentle :) > >Thank you >Kd case of restricting whom can send to whom then you would have a very simple job of setting up distribution groups for all the relevant parties and using the "accept messages from" and "reject messages from" boxes within ADU&C properties of the user on the Exchange server. However, sinceyou want to also want to filter the GAL there is a complication. See: http://www.msexchange.org/tutorials/Shared_Hosting_Exchange_2003_Part1.html for an understanding of what you need to do on an Exchange organisation to filter the GAL for the various users you have. Well, found that the customer wants to have control of who can send
mail to users in the store (thats not the hard part) but definitely limiting who the store users can email back to corporate (thats the tuffy). We did some tests this morning using distribution groups and while we can certainly setup groups as to who can email TO whom if that receiver sends back, they can potentially email anyone in the list (as opposed to just the sender). Thanks...!!! Kd Mark,
I thought it might be easier if you had a little more granular idea of what this customer was wanting. Here's a list of what they would like to accomplish: 1. Corp users must be able to send to anyone externally unrestricted by Exchange 2. Corp users must be able to send to store users but be restricted 3. Corp users can see all users in the GAL 4. Store users must be able to receive mail from Corp Users 5. Store users must be able to reply to mail received from Corp Users 6. Store users must NOT be able to see the GAL - or at least view a limited GAL 7. Store users must only be able to send mail to certain users in Corp regardless of who sends them email What are your thoughts on this? Currently this environment is a single Exchange server. Can you think of ANY way to accomplish this? Are there any 3rd party apps that you know of that can limit the GAL and/or do routing on certain users? Short of creating a new tree and separating the Stores and the Corp I don't see it. TiA... Kd Mark Arnold [MVP] wrote: Show quote > On Sat, 27 May 2006 18:59:18 -0400, Kd <con***@comcast.net> wrote: > >> Hi group, >> Here's the example of my question: >> This is a retail store chain with a corporate headquarters in one >> building and remote stores throughout a local market. The IT department >> wants users in the corporate building to be able to email any users in >> the stores whilst limiting the stores ability to email corporate users. >> >> Most likely they will want the store mgr to be able to reply to whomever >> emails from corporate and then limit the address book of the store user >> to only those corp users that is needed. >> >> The corp uses Exchange 2003 and I believe they only have one server at >> corporate for the time being. I believe the corp is considering putting >> an Exchange Srvr at the remote sites but would this be neccessary? The >> idea is to not have to do so much administration on the server side if >> this can be done by installing a separate server at the sites and use >> Routing Groups and just limiting the users ability to see the Global >> Address list. Or, maybe I have it all wrong and Routing Groups can not >> be used for this? >> >> Any suggestions or comments, ideas welcome. >> >> This is my first time on this list - please, be gentle :) >> >> Thank you >> Kd > > Well, Routing Groups aren't what you need here and if it was simply a > case of restricting whom can send to whom then you would have a very > simple job of setting up distribution groups for all the relevant > parties and using the "accept messages from" and "reject messages > from" boxes within ADU&C properties of the user on the Exchange > server. > > However, sinceyou want to also want to filter the GAL there is a > complication. See: > http://www.msexchange.org/tutorials/Shared_Hosting_Exchange_2003_Part1.html > for an understanding of what you need to do on an Exchange > organisation to filter the GAL for the various users you have. >  |
|||||||||||||||||||||||
Other interesting topics