Cisco Cisco Email Security Appliance C690

Pagina di 24
 
  What’s New in Cisco IronPort AsyncOS 7.1.3 for Email
4
Release Notes for Cisco IronPort AsyncOS 7.1.3 for Email
OL-22161-03
68903
Fixed: DKIM z= Tag Signing Could Create a Header Too Long For RFC 
Compliance.
Previously, when using the z= tag with DKIM signing, multiple recipients could cause 
the DKIM header to exceed the maximum length allowed by SMTP RFC. This could 
cause delivery issues. This issue has been resolved. The z= tag is now turned off by 
default.
71241
Fixed: Multipart/Alternative Messages Result in Double DLP Score.
Previously, when RSA Email DLP scanned a multipart/alternative type message, such 
as HTML messages with a alternative/plain text part, the system combined the 
classifier scores of both parts of the message to create the DLP score. This could result 
in a message that should have a “low severity” score to be rated as high or medium 
severity. This issue has been resolved.
72656
Fixed: Messages with From Header Split Over Two Lines Cannot Be Encrypted.
Fixed an issue where a message cannot be encrypted if its From header is split over 
two lines.
72708
Fixed: Email Scanning Engine Hangs Up While Trying to Decode Invalid UTF-32 
Data.
Fixed an issue where the Email Scanning Engine would crash when attempting to 
process malformed UTF-32 payloads.
69584
Fixed: App Fault Occurs After Appliance with Centralized Reporting Enabled 
Starts Up.
When the Email Security appliance starts up, it performs a scan for corrupted files. 
Previously, if the appliance had centralized reporting enabled, it was possible for an 
exception to occur due to the corruption scan not recognizing timestamp files and 
deleting them. This issue has been resolved. The corruption scan no longer deletes 
these timestamp files.
70468
Fixed: Attachment Filenames Decrypted Incorrectly When the Filename is Split 
Across Multiple Words.
Fixed an issue where the filename of an encrypted message’s attachment was decoded 
incorrectly due to the filename being composed of multiple words. The decoded 
filename would contain an extra space. This could result in applications being unable 
to open the file. The filename now decodes correctly.
Table 1
Resolved Issues in Version 7.1.3 
Defect ID
Description