Cisco Cisco Email Security Appliance C160 Mode D'Emploi

Advanced Configuration Guide. For more information about smart identifiers, see 
“Smart Identifiers” in the “Using Message Filters to Enforce Email Policies” 
chapter of the Cisco IronPort AsyncOS for Email Advanced Configuration Guide.

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.