The FSA can scan the text content of items in Microsoft Exchange Public Folders (for example, calendar events, tasks, or journal entries). In particular, it can scan documents attached to the items.
The FSA can then apply policy to these scanned items and, if necessary, delete them or copy or move them to an alternative location.
Extracting MAPI Properties
The FSA can also extract MAPI properties from items scanned in Exchange Public Folders. It adds these MAPI properties to the metadata for the resulting file event. In turn, this allows Data At Rest policy triggers to test these MAPI properties when applying policy. For example, you may choose to move an attachment to a secure location if the ‘Last Author’ property does not match a list of approved authors.
Why must you specify the individual MAPI properties that you want to extract from scanned items? After all, this is not necessary when scanning file systems for, say, Microsoft Office documents. The reason lies in the method used to store item attributes in Exchange Public Folders.
For Microsoft Office documents stored in a file system, the FSA attempts, as far as possible, to extract all the relevant document properties and add them to the metadata of the resulting file event (the metadata is stored in XML format).
But this approach is not possible for items posted to Exchange Public Folders. The attributes of these items (such as 'Last Author' or 'Sensitivity') are saved as MAPI properties and are too numerous for the FSA to routinely extract all available properties for each item. Instead, you need to configure the FSA scanning job to detect and extract the specific MAPI properties that are relevant to your policy triggers. The triggers can then test these extracted MAPI properties by using XMLATTR data lookup commands.
|
Copyright © 2014 CA.
All rights reserved.
|
|