technicaluser4
Technical User
Does anybody ever had a requirement to prohibit a user from deleting any e-mails from his mailbox?
What is the most practical solution?
What is the most practical solution?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations biv343 on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
How can I restrict a user from deleting his mails
- Thread starter technicaluser4
- Start date
- Status
Journaling doesn't do anything to solve this problem.
What is practical is a large ruler and his knuckles. As Ed Crowley is famous for saying, "There is seldom a technological solution to a behavioral problem."
What you could do, in theory, is reset permissions on his mailbox so that he can't delete the messages. But that's got the potential to cause other issues such as when the user wants to move messages to another folder.
Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.
What is practical is a large ruler and his knuckles. As Ed Crowley is famous for saying, "There is seldom a technological solution to a behavioral problem."
What you could do, in theory, is reset permissions on his mailbox so that he can't delete the messages. But that's got the potential to cause other issues such as when the user wants to move messages to another folder.
Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.
It would be reasonable to suggest that technicaluser4 has a problem that requires the company to maintain all the mail that the deleter hes in his mailbox.
Journaling would solve this
A large ruler and knuckles is not at all practical. As noveyron is famous for saying "make the systems userproof"
I was thinking laterally with my original response. Clearly I was mistaken in doing so, thanks for putting me right Pat.
Journaling would solve this
A large ruler and knuckles is not at all practical. As noveyron is famous for saying "make the systems userproof"
I was thinking laterally with my original response. Clearly I was mistaken in doing so, thanks for putting me right Pat.
Actually, journaling doesn't save all data in the mailbox. Only some. And it increases IOPS extensively. But that's a debate for another time.
The other problem is that you can't make a system "userproof" and have it still be productive for everyone else. At some point, there has to be time when the user needs to be addressed. If the use is deleting mail and shouldn't be, that's a behavioral problem.
Adjusting the mailbox permissions is probably the best way of doing it.
However, if the OP could shed some more light on the situation, the recommendation may change. YMMV.
Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.
The other problem is that you can't make a system "userproof" and have it still be productive for everyone else. At some point, there has to be time when the user needs to be addressed. If the use is deleting mail and shouldn't be, that's a behavioral problem.
Adjusting the mailbox permissions is probably the best way of doing it.
However, if the OP could shed some more light on the situation, the recommendation may change. YMMV.
Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.
SteveRoadWarrior
Technical User
- Jun 13, 2007
- 148
You could send the mail to a public folder, then remove his rights to delete from the public folder. Granted, this brings up additional problems but may work in some scenarios:
For example, in a small company a sales person may get all mail addressed to sales@company.com - he may be inclined to delete messages that he doesn't want any one else to see. A public folder can provide a solution to this type of situation.
CDP solutions that natively read the Exchange store can also address this problem, no rulers required.
For example, in a small company a sales person may get all mail addressed to sales@company.com - he may be inclined to delete messages that he doesn't want any one else to see. A public folder can provide a solution to this type of situation.
CDP solutions that natively read the Exchange store can also address this problem, no rulers required.
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question
- Locked
- Question