Dears, I got one Exchange server 2003 SP2 and I have a very strict outbound email access policy. Only some of the users are allowed to send external emails. The required now is to allow a group of users (that does not have out access) to send to 3 users outside of the exchange org. let's say the recipient emails are : xxxxx@hotmail.com; uuuuuu@gmail.com; yyyyyy@yahoo.com Can this be done and if yes how can i do it? Regards,

Hi, AFAIK natively its not possible maybe there are some third party tools available but I dont think so that its possible with any third party tool. Regards. Shafaquat Ali.M.C.I.T.P Exchange 2007/2010, M.C.I.T.P Windows Server 2008, M.C.T.S OCS Server 2007 R2, URL: http://blog.WhatDoUC.net Phone: +923008210320

Create a new send connector with an address space of just those three recipients, then set the permissions on the connector so that only your user group has permssion to send using that connector.[string](0..33|%{[char][int](46+("686552495351636652556262185355647068516270555358646562655775 0645570").substring(($_*2),2))})-replace " "

Hi, Thanks for the idea it seems to be working one. I will check it also. Regards. Shafaquat Ali.M.C.I.T.P Exchange 2007/2010, M.C.I.T.P Windows Server 2008, M.C.T.S OCS Server 2007 R2, URL: http://blog.WhatDoUC.net Phone: +923008210320

Thx Njolinor for your reply but I cannot do that because i can't add xxxx@hotmail.com only i can add hotmail.com and this is what I don't want to do. Thanks

With Exchange 2003 it is not possible to restrict to a specific email address without third party tools. The closest you can get is the domain level. Exchange operates the "everything except" method, so you could stop users from emailing a specific email address. However it isn't possible to reverse it. Simon.Simon Butler, Exchange MVP. http://blog.sembee.co.uk , http://exbpa.com/

Well darn. I don't have any 2003 left, and was working from memory. I though you could set the namespace down to the recipient level, but apparently I was mistaken. Sorry about that.[string](0..33|%{[char][int](46+("686552495351636652556262185355647068516270555358646562655775 0645570").substring(($_*2),2))})-replace " "

Hi, Its mean my understanding is ok and it cannot be done natively kindly confirm me. Regards. Shafaquat Ali.M.C.I.T.P Exchange 2007/2010, M.C.I.T.P Windows Server 2008, M.C.T.S OCS Server 2007 R2, URL: http://blog.WhatDoUC.net Phone: +923008210320

I think you can do that with a transport rule. Make contacts for the recipients you are restricting. Create the transport rule. Step 1: sent to people, select the contacts. Step 2: choose to send rejection message or delete without notifying anyone. Step 3: except when the message is from people, or better, make a distribution list of allowed senders and choose that. I haven't tested this approach, but it seems like it'd work.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

I think you can do that with a transport rule. Make contacts for the recipients you are restricting. Create the transport rule. Step 1: sent to people, select the contacts. Step 2: choose to send rejection message or delete without notifying anyone. Step 3: except when the message is from people, or better, make a distribution list of allowed senders and choose that. I haven't tested this approach, but it seems like it'd work. Ed Crowley MVP "There are seldom good technological solutions to behavioral problems." He's running 2003.[string](0..33|%{[char][int](46+("686552495351636652556262185355647068516270555358646562655775 0645570").substring(($_*2),2))})-replace " "

On Tue, 28 Sep 2010 09:14:14 +0000, MadRam wrote: >I got one Exchange server 2003 SP2 and I have a very strict outbound email access policy. Only some of the users are allowed to send external emails. The required now is to allow a group of users (that does not have out access) to send to 3 users outside of the exchange org. let's say the recipient emails are : xxxxx@hotmail.com; uuuuuu@gmail.com; yyyyyy@yahoo.com > > > >Can this be done and if yes how can i do it? Yes, it can . . . just not by Exchange 2003. Exchange releases beyoond 2003 can accomplish this by creating a Transport Rule. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

D'oh!Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."