Cisco Cisco Email Security Appliance C160

Virtual appliance 
support 

The following deployment options are now supported: 

Deployments with VMWare ESXi5.1 hypervisor 

Deployment as part of a FlexPod solution 

For general information about FlexPod, see 

Feature keys for individual features can have earlier expiration dates than 
the virtual appliance license, which expires on the date of the 
latest-expiring feature key. 

Virtual license expiration now includes a 180-day grace period, during 
which the appliance continues to deliver mail without security services. 

Option to drop an email 
with corrupt attachment

You can now configure your content and message filters to drop emails 
containing corrupt attachments.

Envelope language

If you are using Cisco Registered Envelope Service for email encryption, you 
can change the locale of the envelope to any one of the following locales: 

English

French 

German 

Spanish 

Portuguese 

Japanese

This feature will not be available at FCS, but will be available some 
time thereafter. 

Provision and activate 
Cisco Registered 
Envelope Service 
administrator from the 
appliance

For physical hardware appliances, you can now provision and activate Cisco 
Registered Envelope Service administrator. The appliance prompts you to 
enter the email address of the encryption account administrator. When you 
provision an Encryption Profile, this email address is registered 
automatically with the encryption server. 

For virtual appliances, see 

Stochastic sampling 

If IronPort Anti-Spam or Intelligent Multi-Scan feature keys are active and 
SenderBase Network Participation is enabled, AsyncOS sends a random 
sample of messages normally dropped by poor reputation to CASE for 
Antispam scanning. CASE scans these messages and uses the results to 
improve the efficacy of the product.

No Operation message 
filter action

AsyncOS now includes a new message filter action, No Operation (

no-op

). 

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.