Cisco Cisco Email Security Appliance X1050 Notas de publicación
13
Release Notes for Cisco AsyncOS 8.5.5 for Email
Known Issues
Known Issues in Release 8.5.5
Known Issues in Release 8.5.0
Reference Number
Description
Some messages are not encrypted as expected.
This can occur if "TLS Required - Verify Hosted Domains" is enabled for
the Destination Domain and the destination Mail Transfer Agent (MTA)
does not offer STARTTLS.
the Destination Domain and the destination Mail Transfer Agent (MTA)
does not offer STARTTLS.
Workaround: Do not enable "TLS Required - Verify Hosted Domains."
Alerts about Python restart.
This occurs only on C170 models, and can occur when:
•
connectivity to the cloud is lost
•
a large number of files is simultaneously uploaded for analysis
Workaround: None
Some SHA values are not displayed in the Completed section of the file
analysis reports page
analysis reports page
Workaround: None
If the File analysis feature key is renewed before the File reputation key is
renewed, the file reputation service does not function.
renewed, the file reputation service does not function.
Workaround: On the Security Services > File Reputation and Analysis
page, disable and then Enable Advanced Malware Protection.
page, disable and then Enable Advanced Malware Protection.
In cluster mode, File analysis should be disabled by default while enabling
Advanced Malware Protection.
Advanced Malware Protection.
Workaround: None
In cluster mode, File Analysis settings cannot be edited on an appliance
with an expired feature key.
with an expired feature key.
Workaround: Login from an Email Security appliance where the feature key
is not expired and edit the File Analysis settings.
is not expired and edit the File Analysis settings.
Reference Number
Description
Inline images are shown as attachments on CRES encrypted messages.
Workaround: Not available
Cisco Web Security Services connection status on URL Filtering page
does not show the connection status of the cluster.
does not show the connection status of the cluster.
Workaround: Not available
URL on the first line of the message body is not detected by URL Filter
in Trace.
in Trace.
Workaround: Add a newline or a text before the URL.