Cisco Cisco Email Security Appliance C380

Pagina di 24
 
  What’s New in Cisco IronPort AsyncOS 7.1.2 for Email
6
Release Notes for Cisco IronPort AsyncOS 7.1.3 for Email
OL-22161-03
69797
Fixed: Generation of Virus Outbreak Filters Report When Virus Outbreak 
Filters is Disabled Causes App Fault.
Previously, the user could generate a Virus Outbreak Filters report even if Virus 
Outbreak Filters were not enabled on the appliance. Doing so would result in an app 
fault. The Virus Outbreak Filters report was added during the System Setup Wizard. 
This issue has been resolved. If Virus Outbreak Filters are not enable on the appliance, 
the user cannot create a report for the feature during the System Setup Wizard.
70185
Fixed: Submit Button Not Working When Using Message Tags in Email DLP 
Policy with IE 7 or 8.
Previously, when creating an Email DLP policy using Internet Explorer 7 or 8, 
specifying a message tag for the policy would cause the Submit button not to work 
properly. Clicking the button failed to submit the Email DLP policy. This issue has 
been resolved.
55558
Fixed: Non-ASCII Character in Recipient Address Causes App Fault.
Fixed an issue where a non-ASCII character in the envelope recipient address caused 
an app fault.
71151
Fixed: Internal Users Summary Report Causes App Fault When Run Over 200 
Days.
Fixed an issue where running an Internal Users Summary Report over a range of more 
than 200 days caused an app fault.
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. 
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 
sslconfig
 CLI command. It continued to use the 
default protocol. This issue has been resolved.
Table 2
Resolved Issues in Version 7.1.2 (continued)
Defect ID
Description