Symantec 10744983 - Mail Security 8320, Administration Manual

Page: 104 / 249

Table 4-8
Additional fields for adding conditions (continued)
Information required Condition
Type the header category (From, To, etc.),
then follow the instructions in the first tow
above.
Message header
Choose a comparison from the first
drop-down list, type a number, and choose
units from the second drop-down list.
Message size
The following table describes the filter tests available for certain conditions when
creating a compliance policy.
Table 4-9
Filter tests
Description Test type
Tests for the supplied text within the component specified.
Sometimes called a substring test. You can in some cases test for
frequency - the number of instances of the supplied text that appear.
Contains/does not
contain
Equivalent to ^text.* wildcard test using matches exactly. Starts with/does not
start with
Equivalent to .*text$ wildcard test using matches exactly. Ends with/does not
end with
Exact match for the supplied text. Matches exactly/does
not match exactly,
Exists/does not exist
Notes:
All text tests are case-insensitive.
Some tests are not available for some components.
Using Perl-compatible regular expressions in conditions
To use regular expressions that behave like Perl regular expressions, click “matches
regular expression” or “does not match regular expression” for either of the
condition options that offer you that choice. The Symantec Mail Security wraps
your regular expression in two forward slashes.
Or you can use a pattern to match certain special characters, including forward
slashes, you must escape each with \ as shown in the table.
Configuring email filtering
Creating virus, spam, and compliance filter policies
104