Link to home
Start Free TrialLog in
Avatar of avogini
avogini

asked on

How to block an email account from emailing anyone externally except for a select few in Exchange 2003?

Explanation:

We have several email accounts that we have set up to only be able to email within our Exchange organization; they are blocked from emailing outside the organization. I did this by simply creating a Connector attached to the First Routing Group (we only have one) which I set to the entire organization in scope, and set the delivery Restrictions to specifically reject messages from these specific accounts.

However now I am being asked if these blocked accounts can now email SPECIFIC external email addresses. To my knowledge I do not think I can be that selective with a block.

So what are my options? Is there a different way to set up a block such as this, yet it would still allow me to punch holes in it for specific external email addresses?

We are running Exchange 2003 SP2 Standard FYI. Thanks for the help!
ASKER CERTIFIED SOLUTION
Avatar of Glen Knight
Glen Knight
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of avogini
avogini

ASKER

I was starting to fear that this exact scenario isn't an option, but as I asked, is there other options available to me to do something similar?
No idea if this will work, but can you set up hidden accounts within the AD schema that automatically forward messages to the allowed external addresses?  this should bypass the connection as the "sender" is one of the accounts that has just been created with forwarding in mind....
Avatar of avogini

ASKER

@Roachy: A possibility, however I don't believe we could set up intelligent rules to filter who they can and cannot send to without having it linked to an Outlook client, which would need to be running...somewhere... Just too many hops at that point for my liking. I may just need to wait for our Exchange 2010 migration in 4th quarter; IF we can do this with 2010...
Avatar of avogini

ASKER

Great, thats for the guide.

However I'm still hopeful someone has a solution for 2003. If not, well that is the way it is. *shrug*
There really isn't other than using the SMTP Event Sink that I have already suggested.
Avatar of avogini

ASKER

Not the answer I was hoping for, but it was an honest answer.