Cisco Cisco Email Security Appliance C690 Notas de publicación
11
Release Notes for Cisco IronPort AsyncOS 7.1.5 for Email Release
OL-22161-05
What’s New in Cisco IronPort AsyncOS 7.1.1 for Email
What’s New in Cisco IronPort AsyncOS 7.1.1 for
Email
This section describes the new features and enhancements added in the Cisco
IronPort AsyncOS 7.1.1 for Email release.
IronPort AsyncOS 7.1.1 for Email release.
69829
Fixed: Emails Exceeding the Maximum Size Do Not Timeout Properly
Previously, there was an issue where the timeout for messages does not work properly
if the message is larger than the configured maximum message size. A response
wouldn’t be sent back to the send and the logs incorrectly indicated that no data was
sent. This issue has been resolved.
if the message is larger than the configured maximum message size. A response
wouldn’t be sent back to the send and the logs incorrectly indicated that no data was
sent. This issue has been resolved.
69573
Fixed: SSL Protocol Modified via sslconfig Does Not Take Effect
In versions 7.1.0 and 7.1.1, the Email Security appliance did not use the SSL protocol
for mail delivery specified using the
for mail delivery specified using the
sslconfig
CLI command. It continued to use the
default protocol. This issue has been resolved.
71152
Fixed: Loading a Configuration file from Previous Appliance to a C370, C670, or
X1070 Takes It Offline After Reboot
X1070 Takes It Offline After Reboot
Fixed an issue where a C370, C670, or X1070 appliance that had configuration files
imported from a previous generation IronPort appliance, such as a C360 or C660,
would go offline after a reboot. Please note that Cisco IronPort does not support the
loading of a configuration file from one appliance model to another.
imported from a previous generation IronPort appliance, such as a C360 or C660,
would go offline after a reboot. Please note that Cisco IronPort does not support the
loading of a configuration file from one appliance model to another.
67137
Fixed: Messages Bounce If an LDAP Server in Chained Masquerade Query is
Unreachable
Unreachable
Previously, if you had a chained masquerade LDAP query configured and the second
LDAP server was unreachable, the message was stuck in the queue in a partially
masqueraded state. When the second LDAP server started to respond again, the
appliance bounced any partially masqueraded messages stuck in the queue. This issue
has been resolved.
LDAP server was unreachable, the message was stuck in the queue in a partially
masqueraded state. When the second LDAP server started to respond again, the
appliance bounced any partially masqueraded messages stuck in the queue. This issue
has been resolved.
Table 3
Resolved Issues in Version 7.1.2 (continued)
Defect ID
Description