Are you asking if someone specifically removes a message from a container or even deletes a container?
There is not alert of any kind if someone did this and there really isn't a method within the product to see that.
Best Practice would be to restrict access to SourceOne storage locations, no one should have access rights to the container or index folders except the SourceOne Service account (group).
SourceOne knows that a specific message is in a specific container.
Index information and SQL Metadata regarding that message exist outside of the container file.
If a container was modified or deleted, if would still be returned by a search but just the message content wouldn't be retrievable.
Gary_Reardon
2 Intern
•
272 Posts
0
December 19th, 2012 09:00
It depends what you mean by recognize.
Are you asking if someone specifically removes a message from a container or even deletes a container?
There is not alert of any kind if someone did this and there really isn't a method within the product to see that.
Best Practice would be to restrict access to SourceOne storage locations, no one should have access rights to the container or index folders except the SourceOne Service account (group).
SourceOne knows that a specific message is in a specific container.
Index information and SQL Metadata regarding that message exist outside of the container file.
If a container was modified or deleted, if would still be returned by a search but just the message content wouldn't be retrievable.