Cisco Cisco Email Security Appliance C160

Page de 13
 
8
Release Notes for Cisco AsyncOS 8.0.1 for Email
 
  Installation and Upgrade Notes
AsyncOS Reversion
If you plan to revert to an earlier version of AsyncOS, such as AsyncOS 7.5.1 or AsyncOS 7.1.5, you 
must update your network settings to use only IPv4 addresses before performing the reversion. Earlier 
releases of AsyncOS for Email do not support IPv6 and any settings that use IPv6 addresses will be reset.
Warning
Cisco does not support reverting your appliances to AsyncOS 7.3.x after you have upgraded them to 
AsyncOS 8.0.1
Re-enable FIPS Mode
If you have upgraded from AsyncOS 7.3, the appliance will not be running in FIPS mode after the 
upgrade. You will need to import or generate new certificates and keys after the upgrade since the 
appliance will not be access the private keys on the HSM.
Re-enable SNMP
SNMP does not start when you boot the appliance after upgrading to AsyncOS 7.6. Use snmpconfig -> 
setup
 and then commit to enable it.
Email Authentication
For DKIM Authentication, IronPort currently supports version 8 of the Draft Specification of 
‘Authentication-Results:’ header.
For SPF/SIDF verification, the 
spf-passed
 rule is no longer available in content filters. To maintain 
backwards compatibility, the spf-passed content filter rule will be accepted from XML configuration 
files but it will be converted to the spf-status rule with corresponding arguments. spf-passed will be 
changed to spf-status == "Pass" and NOT spf-passed to spf-status != "Pass". You can, however, still 
use the spf-passed message filter.
Configuration Files
Cisco IronPort does not generally support the backward compatibility of configuration files with 
previous major releases. Minor release support is provided. Configuration files from previous versions 
may work with later releases; however, they may require modification to load. Check with Cisco 
Customer Support if you have any questions about configuration file support. 
Caution
For important information concerning configuration files and the Email Security virtual appliance, see 
.
Received Headers
When you configure AsyncOS to use received headers, you can specify that the 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