Enterprise Vault™ Setting up Domino Server Archiving
- About this guide
- Setting up Domino mailbox archiving
- About Domino mailbox archiving
- Preparation for Domino mailbox archiving
- Configuring Domino targets, tasks and policies in Enterprise Vault
- Checking the list of Domino forms
- Adding Domino Server archiving targets
- Configuring mailbox policies for Domino mailbox archiving
- General tab (Domino mailbox archiving)
- Archiving Rules tab (Domino mailbox archiving)
- Archiving Actions tab (Domino mailbox archiving)
- Shortcut Content tab (Domino mailbox archiving)
- Forms tab (Domino mailbox archiving)
- Shortcut Deletion tab (Domino mailbox archiving)
- Advanced tab (Domino mailbox archiving)
- Targets tab (Domino mailbox archiving)
- Using customized shortcuts for Domino mailbox archiving
- Domino mailbox archiving retention folders
- Configuring desktop policies for Domino mailbox archiving
- Creating a Domino Provisioning task
- Creating a Domino Mailbox task
- Reviewing the default settings for the Enterprise Vault site
- Adding a Provisioning Group when setting up Domino mailbox archiving
- Installing Enterprise Vault extensions for Notes and DWA clients
- About Enterprise Vault clients for Notes and DWA clients
- Installing Enterprise Vault client extensions for Notes and DWA clients
- Setting up an account to use EVInstall.nsf to set up an Enterprise Vault Domino Gateway
- Setting up an account to use EVInstall.nsf to set up a mail server
- Granting Execution Control List permissions when setting up Notes and DWA clients
- Installing the Notes and DWA client extensions
- Changes made by EVInstall.nsf when setting up Domino mailbox archiving
- EVInstall.nsf changes on Domino 9.0 and later Enterprise Vault Domino Gateways
- EVInstall.nsf changes on Domino 8.5 Enterprise Vault Domino Gateways
- EVInstall.nsf changes on Domino 9.0 and later mail servers
- EVInstall.nsf changes on Domino 8.5 mail servers
- EVInstall.nsf changes on Domino 8 mail servers
- Updating mail files with the new design after installing the Notes and DWA extensions
- How users access Enterprise Vault Search features after installing the Notes and DWA extensions
- Identifying internal Notes mail recipients
- How to edit automatic messages after installing Domino mailbox archiving
- Enabling mailboxes for archiving after installing Domino mailbox archiving
- Setting up a Vault Cache for offline users
- Setting up Domino Journaling archiving
- Preparation for Domino Journaling archiving
- Adding a Domino domain
- Adding a Domino server
- Assigning a vault store for Domino Journaling
- Creating a Domino Journal archive
- Adding permissions to the Domino journal archive
- Creating a Domino Journal policy
- Creating a Domino Journaling task
- Adding a Domino Journaling location
- Identifying internal Notes mail recipients
- How to configure clients when setting up Domino Journal archiving
- Configuring filtering
- About filtering
- Configuring custom filtering
- Configuring registry settings for Domino 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
- Message author and recipients filters for custom filtering
- About distribution lists in attribute values with custom filtering
- About creating complex filters using the INCLUDES and ALLOWOTHERS operators
- Message direction filters for custom filtering
- Message subject filters for custom filtering
- Domino named property filters for custom filtering
- Example ruleset file for custom filtering
- Configuring custom properties and content categories
- About the general format of Custom Properties.xml
- Defining additional Domino message properties in custom properties
- About content categories
- Defining how custom properties are presented in third party applications
- Summary of custom property elements and attributes
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.
