Cisco Cisco Email Security Appliance X1070 릴리즈 노트
11
Release Notes for Cisco IronPort AsyncOS 7.5.1 for Email
OL-25139-02
Installation Notes
SNMP Monitoring: More Open Files
If you are monitoring Email Security appliances using SNMP, the number of open
files will increase to around 2500 after upgrading the appliance to AsyncOS 7.5.1.
files will increase to around 2500 after upgrading the appliance to AsyncOS 7.5.1.
Email Authentication
For DKIM Authentication, IronPort currently supports version 8 of the Draft
Specification of ‘Authentication-Results:’ header.
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.
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
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 IronPort Customer Support if
you have any questions about configuration file support.
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 IronPort 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:
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.
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 strip-header filter action configured to strip received
headers will strip the received header inserted by AsyncOS. [Defect IDs: 16254,
25816]
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]