mhorrocks
asked on
Restricting SMTP traffic for a group of users
I am running Exchange 2000 on a Windows 2000 server. I need to know if there is a way to restrict smtp traffice for a user. I know how to totally restrict a user so that they can only communicate via x400.
I want to restrict a user to be only able to send and receive emails from 1 outside recipient and of course still be able to send and receive exchange (x400) messages. So to try and make it simple, I want a user to be able to send and receive emails from anyone within the exchange organization, but only want them to be able to send and receive emails from one (1) outside source (anyone@aol.com), all other outside email (smtp) would be rejected and any attempt to send to anyone other than the specified account would be rejected.
Any Ideas?
I thought of creating an exchange user and having all mail delivered to that address be forwarded to the outside email account (anyone@aol.com), this would allow the exchange user to send an email to that account and it would be forwarded to anyone@aol.com. This solves the outgoing issue but does nothing for incoming mail from anyone@aol.com because it would go that special account I created and be forwarded right back to them.
Please be specific with your replies. I am assigning this question 500 points because I want specific details on how to accomplish this.
I want to restrict a user to be only able to send and receive emails from 1 outside recipient and of course still be able to send and receive exchange (x400) messages. So to try and make it simple, I want a user to be able to send and receive emails from anyone within the exchange organization, but only want them to be able to send and receive emails from one (1) outside source (anyone@aol.com), all other outside email (smtp) would be rejected and any attempt to send to anyone other than the specified account would be rejected.
Any Ideas?
I thought of creating an exchange user and having all mail delivered to that address be forwarded to the outside email account (anyone@aol.com), this would allow the exchange user to send an email to that account and it would be forwarded to anyone@aol.com. This solves the outgoing issue but does nothing for incoming mail from anyone@aol.com because it would go that special account I created and be forwarded right back to them.
Please be specific with your replies. I am assigning this question 500 points because I want specific details on how to accomplish this.
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
MHorrocks:
It might not hurt to post a 20 point "pointer" question linking back to this one in order to try and gen more responses.
Unfortunately there are just not that many needs to restrict employees to sending mail to certain places. There are plenty of needs to restrict mail out there, but they only occasionally come up. Most of the time it is an HR issue...and like all HR issues...it becomes time to write the usage guidelines policy.
It might not hurt to post a 20 point "pointer" question linking back to this one in order to try and gen more responses.
Unfortunately there are just not that many needs to restrict employees to sending mail to certain places. There are plenty of needs to restrict mail out there, but they only occasionally come up. Most of the time it is an HR issue...and like all HR issues...it becomes time to write the usage guidelines policy.
ASKER
I met with representatives of Microsoft on Friday and there response was that in Exchange 2003 running on Microsoft Server 2003 I will be able to accomplish my task cleanly with policies. This is not available in 2000 only in 2003. So we are setting timetables to upgrade to 2003 late this summer.
Thank you for your detailed and honest remarks. I graded you an "A".
Thank you for your detailed and honest remarks. I graded you an "A".
Exchange 2003 seems to always be the answer.
Fortunately, an Exchange 2003 migration is not as painful as 5.5 to 2000 was. Good luck!
Thanks for the grade!
Fortunately, an Exchange 2003 migration is not as painful as 5.5 to 2000 was. Good luck!
Thanks for the grade!
ASKER
You definitely laid it out step by step, thank you very much.
If no one can give me an alternative, such as third party software then this answer will be accepted and the points awarded to "flyguybob".
I will leave this question open for an additional 8 hours and then close. I must present a solution today, or open the outside world to these users for email.
I remember a long time ago, when I wanted to restrict my users internet access to just those sites that I gave them access to and not just have a list of sites that access was denied. I couldn't find a piece of software that attacked that problem from the bottom up. I wanted to deny them everything and just allow them access to approved sites, this just didn't exist 12 years ago. Now it does. It is a shame that this approach has not yet made it to the Email world, I wonder what that would do to spammers???? Hmmm.... If anyone knows of software that will accomplish, please share it with me.