Cisco Cisco Email Security Appliance C170 사용자 가이드

0 - Apply this action to all messages 

The syntax of a filter using the 

url-category-replace

 action is 

<msg_filter_name>:

if <condition> 

{

url-category-replace([‘<category-name1>’,’<category-name2>’,…, 

‘<category-name3>’],’<replacement-text>’, ’<url_white_list>’, <unsigned-only>);

}

Where 

replacement-text

 is the text that you want to use to replace the URL. 

The syntax of a filter using the 

url-category-defang 

action is: 

<msg_filter_name>:

if <condition>

{

url-category-defang([‘<category-name1>’,’<category-name2>’,…, ‘<category-name3>’], 

’<url_white_list>’, <unsigned-only>);

}

The syntax of a filter using the 

url-category-proxy-redirect 

action is: 

<msg_filter_name>:

if <condition>

{

url-category-proxy-redirect([‘<category-name1>’,’<category-name2>’,…, 

‘<category-name3>’], ’<url_white_list>’, <unsigned-only>);

}

The No Operation action performs a no-op, or no operation. You can use this action in a message filter 
if you do not want to use any of the other actions such as Notify, Quarantine, or Drop. For example, to 
understand the behavior of a new message filter that you created, you can use the No Operation action. 
After the message filter is operational, you can monitor the behavior of the new message filter using the 
Message Filters report page, and fine-tune the filter to match your requirements.

The following example shows how to use No Operation action in a message filter.

new_filter_test: if header-repeats ('subject', X, 'incoming') {no-op();}