Cisco Cisco Email Security Appliance C680 Release Notes

Page of 18
 
13
Release Notes for Cisco AsyncOS 8.5.6 for Email
 
  Resolved Issues
Resolved Issues in Cisco AsyncOS 8.5.6 for Email
Reference Number
Description
You may intermittently see application faults and alerts when some of the 
incoming SMTP connections over TLS are closed.
Logging into the web interface of a virtual appliance causes an application fault.
When using the Centralized Policy/Virus/Outbreak Quarantines, you may 
receive an application fault.
Delivering an email over a TLS connection fails.
Emails to addresses with same username but different domain names are 
dropped as duplicates.
Authentication queries when using LDAP chain queries fails. 
Some of the malicious URLs are bypassed.
Unable to load the cluster configuration. When loading the cluster 
configuration, you are prompted to save a .json file or the next window does not 
appear.
You may see application faults when messages from Centralized Quarantine on 
SMA are released or deleted. 
LDAP chained query disappears from the drop down menu when the name of the 
query contains the character "/".
An application fault occurs whenever you access the Monitor > Scheduled 
Reports
 page.
Machines installed with OpenSSL 1.0.1g patch fail to connect with Cisco Email 
Security Appliance.
Virtual appliances are not generating unique Client ID for File Analysis.
Throttle requests to SDS daemon when under load.
Cluster commits or resynchronizations take several minutes to complete and are 
prone to fail.
Emails are sent unencrypted when 'TLS Required - Verify Hosted Domains' 
option is enabled for the destination domain and the destination MTA does not 
provide STARTTLS.
Tarpit can only be set to 35%.
URL Filtering slows emails when SDS server is unreachable.
Vulnerabilities in OpenSSL affecting Cisco AsyncOS for Email. For more 
information, see 
Email Security appliance lags due to excessive memory usage of URL Filtering 
Client Service.
Any message having badly encoded data or an unknown encoding in the 
“friendly” FROM header that is sent to a user whose address is being checked 
for masquerade will cause an application fault and cause the message to bounce.