Cisco Cisco Email Security Appliance C670

Pagina di 24
 
  Fixed Issues
18
Release Notes for Cisco IronPort AsyncOS 7.1.3 for Email
OL-22161-03
Fixed Issues
The following issues have been fixed in the AsyncOS 7.1 for Email release.
Table 4
Resolved Issues in Version 7.1 
Defect ID
Description
67002
Fixed: Invalid Regular Expressions Halt RSA Email DLP Scanning.
Previously, entering an invalid regular expression for a RSA Email DLP policy caused 
an application fault that halted DLP scanning even if the regular expression was later 
corrected. While the AsyncOS GUI validates regular expressions, it may not catch all 
errors. There were two known regular expression errors that could cause this 
application fault:
  •
the repeat construct, which is represented as brackets (
{}
), if the brackets are 
empty or contain something other than a single number or two numbers separated 
by a comma, and
  •
a regular expression begins or ends with the “or” construct, which is represented 
as a vertical bar (
|
).
This issue has been resolved. The AsyncOS GUI now tests for the above regular 
expression errors.
52407
Fixed: Message Tracking Details Page Displays Masking Backslashes in Content 
Matching Classifiers Containing Single Quotation Marks.
Previously, the DLP Matched Content tab on the Message Tracking Details page 
erroneously displays masking backslashes preceding single quotation marks in 
content matching classifiers. For example, 
"b'lad"e '''"2"
' appears as 
"b\'lad"e\'\'\'"2"\'
. This issue has been resolved.
55874
Fixed: Application Fault Occurs When Switching Cluster Levels in Encryption 
Profile.
Previously, an application fault occurred when switching between different cluster 
levels on the Encryption Profile page in the GUI. This issue has been resolved.
37164
Fixed: Corrupted Uuencoded Content Results in Warning and Skipped Filters.
Previously, a message with a corrupted uuencoded attachment caused the Email 
Security appliance to skip message filters processing and record a warning in the mail 
logs. This issue has been resolved. Now, the appliance applies filters to messages with 
corrupted uuencoded content.