Cisco Cisco Email Security Appliance C670 Release Notes
![Cisco](https://files.manualsbrain.com/attachments/7380d0050044647c30f5c24bbbf5d0c0b6d9bb84/common/fit/150/50/faa183d287233c52228cfea3dbc2a127fe780f60564fcb0955d9c3d1cd23/brand_logo.png)
11
Release Notes for Cisco IronPort AsyncOS 7.1.2 for Email
OL-22161-03
Installation Notes
Custom Notification Templates
If you previously used a custom notification template, headers were included by
default. When you upgrade to AsyncOS version 5.0 or later, notification templates
do not include headers by default. To include headers, you can add the
default. When you upgrade to AsyncOS version 5.0 or later, notification templates
do not include headers by default. To include headers, you can add the
$allheaders
message filter action variable. [Defect ID: 27710]
Received Headers
When you configure AsyncOS to use received headers, you can specify that the
header reflects one of the following hostnames:
header reflects one of the following hostnames:
•
The hostname of the Virtual Gateway used for delivering the message
•
The hostname of the interface the message is received on
You specify the hostname from the CLI command
listenerconfig-> setup
. You
cannot configure the hostname from the GUI.
If you configure the received header to display the hostname of the interface the
message is received on, a
message is received on, a
strip-header
filter action configured to strip received
headers will strip the received header inserted by AsyncOS. [Defect IDs: 16254,
25816]
25816]
Feature Keys
The AsyncOS appliance checks for and applies feature keys at one minute
intervals. Therefore, when you add a feature key, it may take up to a minute to
view the changes. [Defect ID: 29160]
intervals. Therefore, when you add a feature key, it may take up to a minute to
view the changes. [Defect ID: 29160]
Upgrading to the AsyncOS 7.1.2 Release
For the AsyncOS 7.1.2 release, please use the following instructions to upgrade
your Email Security appliance.
your Email Security appliance.
Step 1
Save the XML configuration file off the IronPort appliance.
Step 2
If you are using the Safelist/Blocklist feature, export the Safelist/Blocklist
database off the IronPort appliance.
database off the IronPort appliance.
Step 3
Suspend all listeners.