Cisco Cisco Email Security Appliance C160 Mode D'Emploi

Page de 1219
 
9-100
Cisco AsyncOS 9.1 for Email User Guide
 
Chapter 9      Using Message Filters to Enforce Email Policies
  Using the CLI to Manage Message Filters
The first prompt determines whether or not a message header’s encoding should be changed to match 
that of the message body if the header is changed (via a filter, for example).
The second prompt controls whether or not the appliance should impose the encoding of the message 
body on the header if the header is not properly tagged with a character set.
The third prompt is used to configure how disclaimer stamping (and multiple encodings) in the message 
body works. Please see “Disclaimer Stamping and Multiple Encodings” in the “Text Resources” chapter 
for more information.
Sample Message Filters
In the following example, the 
filter
 command is used to create three new filters:
The first filter is named 
big_messages
. It uses the 
body-size
 rule to drop messages larger than 10 
megabytes. 
The second filter is named 
no_mp3s
. It uses the 
attachment-filename
 rule to drop messages that 
contain attachments with the filename extension of 
.mp3
The third filter is named 
mailfrompm
. It uses 
mail-from
 rule examines all mail from 
postmaster@example.com
 and blind-carbon copies 
administrator@example.com
always try to use the message body's encoding for the footer or 
heading. If that fails, and if the message body's encoding is US-
ASCII, the system can try to edit the message body to use the footer's 
or heading's encoding. Should the system try to impose the footer's 
or headings's encoding on the message body? [N]> y
Behavior when modifying headers: Use encoding of message body
Behavior for untagged non-ASCII headers: Impose encoding of message 
body. Behavior for mismatched footer or heading encoding: Try both 
body and footer or heading encodings
Choose the operation you want to perform:
- SETUP - Configure multi-lingual settings.