Enterprise Vault™ Setting up Exchange Server Archiving
- About this guide
- Distributing Exchange Server Forms
- Setting up archiving from mailboxes
- Points to note before you set up Enterprise Vault mailbox archiving
- Defining Exchange Server mailbox archiving policies
- Mailbox policy settings when setting up Exchange Server archiving
- Mailbox policy settings when setting up Exchange Server archiving
- Defining desktop policies in Exchange Server archiving
- Desktop policy settings in Exchange Server archiving
- Options tab (Exchange Server archiving desktop policy setting)
- Advanced tab (Exchange Server archiving desktop policy setting)
- Desktop policy settings in Exchange Server archiving
- Adding Exchange Server archiving targets
- Using customized shortcuts with Exchange Server archiving
- About editing automatic messages for Exchange Server archiving
- Enabling mailboxes for Exchange Server archiving
- Setting up users' desktops
- Enterprise Vault Outlook Add-In for Exchange Server archiving
- Enterprise Vault Client for Mac OS X with Exchange Server archiving
- Getting users started with Exchange Server archiving
- Setting up Vault Cache and Virtual Vault
- Vault Cache synchronization
- Vault Cache header synchronization and content download
- Vault Cache advanced settings
- Virtual Vault advanced settings
- Setting up archiving from public folders
- About public folder policy settings
- Exchange Public Folder policy settings
- Exchange Public Folder policy settings
- Adding public folder archiving targets
- Setting up archiving of journaled messages
- Envelope Journaling
- Setting up Enterprise Vault Office Mail App for Exchange Server 2013 and later
- About the Enterprise Vault Office Mail App
- Deploying the Enterprise Vault Office Mail App
- Troubleshooting the Enterprise Vault Office Mail App
- Setting up Enterprise Vault access for OWA clients on Exchange Server 2010
- About Enterprise Vault functionality in OWA clients
- Enterprise Vault OWA Extensions in an Exchange Server 2010 environment
- Configuring access to Enterprise Vault from Outlook RPC over HTTP clients
- Using firewall software for external access to OWA and Outlook
- Configuring filtering
- About filtering
- Configuring selective journaling
- Configuring group journaling
- Configuring custom filtering
- About custom filtering ruleset files
- About controlling default custom filtering behavior
- About the general format of ruleset files for custom filtering
- About rule actions for custom filtering
- About message attribute filters for custom filtering
- About the general format of Custom Properties.xml
- About content categories
- Defining how custom properties are presented in third party applications
- Custom properties example
About creating complex filters using the INCLUDES and ALLOWOTHERS operators
You can create more complex filters by specifying several values for AUTHOR, RECIPIENTS, SUBJECTS, and NAMEDPROP message attributes and using the operators, INCLUDES= and ALLOWOTHERS=, to define how the attribute values are to be matched.
INCLUDES= can have the following values:
INCLUDES="NONE" means match messages that do not include the values specified for the attribute
INCLUDES="ANY" means match messages that include one or more of the values specified for the attribute
INCLUDES="ALL" means match messages that include all of the values specified for the attribute
If the INCLUDES= operator is not specified, INCLUDES="ANY" is assumed.
ALLOWOTHERS= can have the following values:
ALLOWOTHERS="N" means match messages that include only the values specified in the filter and no others
ALLOWOTHERS="Y" means that matched messages can include attribute values other than those listed in the filter can be included
If the ALLOWOTHERS= operator is not specified, ALLOWOTHERS="Y" is assumed.
This section provides examples of how you can use the INCLUDES= and ALLOWOTHERS= operators with RECIPIENTS message attributes.
In the following example, messages will match the rule if they have all three of the listed email addresses (INCLUDES="ALL"), and only these addresses (ALLOWOTHERS="N"), in the recipient list:
<RULE ... > <RECIPIENTS INCLUDES="ALL" ALLOWOTHERS="N"> <EA>john.doe@ourcompany.com</EA> <EA>ken.brookes@ourcompany.com</EA> <EA>len.scott@ourcompany.com</EA> </RECIPIENTS> </RULE>
In the next example, messages will match the rule if they have any of the listed email addresses (INCLUDES="ANY") but nothing else (ALLOWOTHERS="N"):
<RULE ... > <RECIPIENTS INCLUDES="ANY" ALLOWOTHERS="N"> <EA>john.doe@ourcompany.com</EA> <EA>ken.brookes@ourcompany.com</EA> <EA>len.scott@ourcompany.com</EA> </RECIPIENTS> </RULE>
In the next example, messages will match the rule if they do not include any of the listed email addresses in the recipient list (INCLUDES="NONE"). Matched messages can have other addresses in the recipient list (ALLOWOTHERS="Y"):
<RULE ... > <RECIPIENTS INCLUDES="NONE" ALLOWOTHERS="Y"> <EA>john.doe@ourcompany.com</EA> <EA>ken.brookes@ourcompany.com</EA> <EA>len.scott@ourcompany.com</EA> </RECIPIENTS> </RULE>
If you want to specify both positive and negative matches within a single rule, you can have multiple message attribute entries and use INCLUDES="NONE" or INCLUDES="ALL", as appropriate. For example:
<RULE ... > <RECIPIENTS INCLUDES="NONE"> <EA>john.doe@ourcompany.com</EA> <EA>len.scott@ourcompany.com</EA> </RECIPIENTS> <RECIPIENTS> INCLUDES="ALL"> <EA>Ken.Brookes@ourcompany.com</EA> <EA>robert.hill@ourcompany.com</EA> </RECIPIENTS> </RULE>
In the above example, messages will match if they do not include john.doe@ourcompany.com or len.scott@ourcompany.com in the recipient list:
<RECIPIENTS INCLUDES="NONE" ...</RECIPIENTS>
but do include both ken.brookes@ourcompany.com and robert.hill@ourcompany.com
<RECIPIENTS INCLUDES="ALL" ... </RECIPIENTS>
By using different combinations of INCLUDES= and ALLOWOTHERS= values, you can set fairly complex filters.
Table: Effect of using different operator value combinations shows filter results for different messages when different combinations of values are set for the operators, INCLUDES= and ALLOWOTHERS=, in the following example filter:
<RULE ... ACTION="ARCHIVE_ITEM"> <RECIPIENTS INCLUDES="NONE|ANY|ALL" ALLOWOTHERS="N|Y"> <EA>Ann@example.com</EA> <EA>Bill@example.com</EA> </RECIPIENTS> </RULE>
Ann@example.com and Bill@example.com are the recipient addresses to match.
Table: Effect of using different operator value combinations
Operator values set | Msg 1: recipient is Ann | Msg 2: recipients are Ann & Bill | Msg 3: recipients are Ann, Bill & Colin | Msg 4: recipients are Bill & Colin | Msg 5: recipient is Colin |
---|---|---|---|---|---|
INCLUDES="NONE" + ALLOWOTHERS="Y" | no match | no match | no match | no match | match |
INCLUDES="NONE "+ ALLOWOTHERS="N" | no match | no match | no match | no match | no match |
INCLUDES="ANY "+ ALLOWOTHERS="Y" | match | match | match | match | no match |
INCLUDES="ANY" + ALLOWOTHERS="N" | match | match | no match | no match | no match |
INCLUDES="ALL" + ALLOWOTHERS="Y" | no match | match | match | no match | no match |
INCLUDES="ALL" + ALLOWOTHERS="N" | no match | match | no match | no match | no match |
In the table, the main column headings show the recipients in five different test messages. (For brevity, the recipients are called Ann, Bill, and Colin in the column headings.)
The first column shows different combinations of values set for the INCLUDES= and ALLOWOTHERS= operators.
"no match" means that, if the operator combination shown in the left column is set, a message sent to the recipients shown in the column heading would not satisfy the filter rule and would not be archived (that is, the rule action is not applied).
"match" means that, if the operator combination shown in the left column is set, a message sent to the recipients shown in the column heading would satisfy the filter rule and be archived.
Figure: Msg 1 with INCLUDES="NONE" and ALLOWOTHERS="N" and Figure: Msg 1 with INCLUDES="ANY" and ALLOWOTHERS="Y" illustrate what happens in two of the scenarios in Table: Effect of using different operator value combinations.