Cisco Cisco Email Security Appliance C160
9
Release Notes for Cisco AsyncOS 8.5.6 for Email
Installation and Upgrade Notes
Provisioning and Activating Cisco Registered Envelope Service Administrator from Virtual
Appliances
Appliances
Please contact Cisco TAC for information required to provision your virtual appliance.
Pre-upgrade Notes
Please be aware of the following upgrade impacts:
•
•
•
•
•
Email Authentication
For DKIM Authentication, Cisco currently supports version 8 of the Draft Specification of
‘Authentication-Results:’ header.
‘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.
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 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.
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.
Received Headers
When you configure AsyncOS to use received headers, you can specify that the header reflects one of
the following hostnames:
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 web interface.
hostname from the web interface.
If you configure the received header to display the hostname of the interface the message is received on,
a strip-header filter action configured to strip received headers will strip the received header inserted
by AsyncOS.
a strip-header filter action configured to strip received headers will strip the received header inserted
by AsyncOS.