Cisco Cisco Email Security Appliance C680 Release Notes
3
Release Notes for Cisco IronPort AsyncOS 7.1.5 for Email Hot Patch Release
OL-22161-04
What’s New in Cisco IronPort AsyncOS 7.1.5 for Email
What’s New in Cisco IronPort AsyncOS 7.1.5 for
Email
This section describes the resolved issues in the Cisco IronPort AsyncOS 7.1.5 for
Email release.
Email release.
Fixed Issues
Table 2
Resolved Issues in Version 7.1.5
Defect ID
Description
22164
Fixed: Regular Expression that Exceeds Data Limit Invalidates Message Filter
Previously, if certain data caused a failure when evaluating a message filter’s regular
expression, an application fault occurred and the message filter became invalidated.
This issue has been resolved. Now, the appliance skips the message filter for that
message without invalidating the filter for subsequent messages.
expression, an application fault occurred and the message filter became invalidated.
This issue has been resolved. Now, the appliance skips the message filter for that
message without invalidating the filter for subsequent messages.
74473
Fixed: version Command Displays RAID Type as ‘NA’
Fixed an issue where the
version
command would display the RAID type as
NA
due
to improper RAID controller parsing heuristics. This issue affects the following areas:
•
CLI: the
version
command didn’t display the correct RAID volume state.
•
SNMP: would mark all disks down at boot and fire notifications for all disks, due
to an invalid state change.
to an invalid state change.
51946
Fixed: LDAP Masquerade Query Cannot Process To: Headers that Do Not
Conform to RFC 2047
Conform to RFC 2047
Previously, an LDAP masquerade query would not be able to process a message with
a non-English “To:” header where the email address is also encoded and does not
conform to RFC 2047. The message would get stuck in the queue. This issue has been
resolved. Now, the appliance decodes and re-encodes a non-compliant To: header and
performs the correct LDAP masquerade query.
a non-English “To:” header where the email address is also encoded and does not
conform to RFC 2047. The message would get stuck in the queue. This issue has been
resolved. Now, the appliance decodes and re-encodes a non-compliant To: header and
performs the correct LDAP masquerade query.