Cisco Cisco Email Security Appliance C690

Seite von 28
 
  What’s New in Cisco IronPort AsyncOS 7.1.5 for Email
4
Release Notes for Cisco IronPort AsyncOS 7.1.5 for Email Release
OL-22161-05
51946
Fixed: LDAP Masquerade Query Cannot Process To: Headers that Do Not 
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.
75798
Fixed: End User Quarantine Always Uses Demo Certificate for LDAP 
Connections
Fixed an issue where the End User Quarantine always used the Demo Certificate for 
LDAP connections instead of the certificate that the user configured the appliance to 
use for LDAP connections.
72606
Fixed: Excessive Memory Usage When Archiving Large Unscannable Messages
Previously, the appliance would run out of memory when it attempted to archive a 
very large message that could not be scanned by the anti-virus scanning engine. This 
issue has been resolved.
55358
Fixed: Excessive Unclaimed Memory After DKIM Signing and Verification
Previously. the appliance would have unclaimed memory after performing DKIM 
signing or verification. Appliances performing frequent DKIM signing and 
verification would eventually run out of memory. This issue has been solved.
74972
Fixed: Quarantined Messages with Older than Hard Bounce Timeout May be 
Bounced When Released
Previously, messages that stay in a system quarantine longer than the timeout for hard 
bounces would be bounced if the destination server was not available when a message 
was released. The appliance also bounced an older message if the destination queue 
had more than 5000 messages, even if the destination server was available. This issue 
has been resolved.
76664
Fixed: Reporting Goes Out of Operation Due to Resources Leak
Fixed an issue where the Reporting feature goes out of operation due to a resources 
leak on the appliance when a report query errors out. The appliance would incorrectly 
display an error message stating that the maximum number of concurrent queries has 
been exceeded when this issue occurred.
Table 1
Resolved Issues in Version 7.1.5 
Defect ID
Description