Cisco Cisco Email Security Appliance C370D Release Notes
2
Release Notes for AsyncOS 9.7.2 for Cisco Email Security Appliances
What’s New
What’s New in AsyncOS 9.7.2
What’s New in AsyncOS 9.7.1
Feature
Description
Support for 90-Series
Hardware
Hardware
Support for new appliance models:
•
C190
•
C390
•
C690
Using From Header for
DKIM Signing
DKIM Signing
You can now use the DKIM Global Settings (Mail Policies > Signing
Profiles) to choose whether to use From header for DKIM signing. For
DMARC verification of DKIM signed messages, you must use the From
header during DKIM signing.
Profiles) to choose whether to use From header for DKIM signing. For
DMARC verification of DKIM signed messages, you must use the From
header during DKIM signing.
Duplicate Boundaries
Verification
Verification
Cisco Email Security appliance can now detect messages with duplicate
MIME boundaries and perform actions on them.
MIME boundaries and perform actions on them.
Use the Duplicate Boundaries Verification content filter condition or the
duplicate_boundaries
message filter rule to detect messages with
duplicate MIME boundaries.
Example
The following message filter will quarantine all the messages that contain
duplicate MIME boundaries.
duplicate MIME boundaries.
DuplicateBoundaries: if (duplicate_boundaries) {
quarantine("Policy"); }
Feature
Description
URL Filtering
Enhancement
Enhancement
You can now configure the appliance not to replace the URLs within
HREF tags with secure proxy URLs. However, if an end user clicks on
these URLs, the end user will be redirected to the secure proxy.
HREF tags with secure proxy URLs. However, if an end user clicks on
these URLs, the end user will be redirected to the secure proxy.
You can configure this option using the
websecurityadvancedconfig
command in CLI (
websecurityadvancedconfig
>
Do you want to
rewrite all URLs with secure proxy URLs? [Y]> n
).
Message Filter Rule to
Detect Malformed MIME
Headers
Detect Malformed MIME
Headers
You can now take actions on messages with malformed MIME headers
using the new message filter rule: “
using the new message filter rule: “
malformed-header
.” The following
example shows how to quarantine all the messages with malformed MIME
headers:
headers:
quarantine_malformed_headers: if (malformed-header)
{
quarantine("Policy");
}