Cisco Cisco Email Security Appliance C170 Guia Do Utilizador

For each term, you specify a “weight,” so that certain terms can trigger filter conditions more easily. 
When AsyncOS scans messages for the content dictionary terms, it “scores” the message by multiplying 
the number of term instances by the weight of term. Two instances of a term with a weight of three would 
result in a score of six. AsyncOS then compares this score with a threshold value associated with the 
content or message filter to determine if the message should trigger the filter action. 

You can also add smart identifiers to a content dictionary. Smart identifiers are algorithms that search 
for patterns in data that correspond to common numeric patterns, such as social security numbers and 
ABA routing numbers. These identifiers can useful for policy enforcement. For more information about 
regular expressions, see “Regular Expressions in Rules” in the “Using Message Filters to Enforce Email 
Policies” chapter. For more information about smart identifiers, see “Smart Identifiers” in the “Using 
Message Filters to Enforce Email Policies” chapter.

Dictionaries containing non-ASCII characters may or may not display properly in the CLI on your 
terminal. The best way to view and change dictionaries that contain non-ASCII characters is to export 
the dictionary to a text file, edit that text file, and then import the new file back into the appliance. For 
more information, see 

In some languages (double-byte character sets), the concepts of a word or word boundary, or case do not 
exist. Complex regular expressions that depend on concepts like what is or is not a character that would 
compose a word (represented as “\w” in regex syntax) cause problems when the locale is unknown or if 
the encoding is not known for certain. For that reason, you may want to disable word-boundary 
enforcement.

The content dictionary feature also includes, by default, the following text files located in the 
configuration directory of the appliance: 

config.dtd

 

profanity.txt

proprietary_content.txt

sexual_content.txt

These text files are intended to be used in conjunction with the content dictionaries feature to aid you in 
creating new dictionaries. These content dictionaries are weighted and use smart identifiers to better 
detect patterns in data and trigger filters when the patterns indicate compliance issues. 

Importing and exporting dictionaries does not preserve the Match Whole Words and Case Sensitive 
settings. This settings are only preserved in the configuration file.

See 

 for more information accessing on the 

configuration directory.