Cisco Cisco Email Security Appliance C170
6
Release Notes for AsyncOS 9.8 for Cisco Email Security Appliances
Changes in Behavior
Changes in Behavior
Marketing Email Settings
If you had enabled anti-spam scanning and had configured Marketing
Email Settings under anti-spam settings for a mail policy, after upgrading
to AsyncOS 9.8 or later,
Email Settings under anti-spam settings for a mail policy, after upgrading
to AsyncOS 9.8 or later,
•
Graymail will be enabled globally by default.
•
Marketing Email Settings under anti-spam settings will be moved
under graymail settings of the same policy.
under graymail settings of the same policy.
•
While using graymail-related reports, keep in mind that:
–
The number of marketing messages is a sum of marketing
messages detected before and after the upgrade.
messages detected before and after the upgrade.
–
The total number of graymail messages does not include the
number of marketing messages detected before the upgrade.
number of marketing messages detected before the upgrade.
–
The total number of attempted messages also includes the number
of marketing messages detected before the upgrade.
of marketing messages detected before the upgrade.
Content Dictionary
Changes
Changes
For efficient processing, the following content dictionary entries are
treated as words:
treated as words:
•
Entries containing only alphanumeric characters
•
Email addresses containing the following characters: 0-9, A-Z, a-z,
dot, underscore, hyphen, and at symbol
dot, underscore, hyphen, and at symbol
•
Domain names containing the following characters: 0-9, A-Z, a-z, dot,
underscore, hyphen, and at symbol
underscore, hyphen, and at symbol
If you want the appliance to treat such a word as a regular expression,
enclose the word in parenthesis, for example,
enclose the word in parenthesis, for example,
(user@example.com)
.
File Analysis
File Analysis changes may require action from you. See
.
DKIM Signing-related
Logging Changes
Logging Changes
•
If the log level is set to Trace, the mail log will now include additional
log entries to identify errors that occur during the DKIM signing
process.
log entries to identify errors that occur during the DKIM signing
process.
•
The mail log will now include two separate log entries for DKIM
signing: one for displaying the signing profile that will be used for the
signing and the other for the signing event.
signing: one for displaying the signing profile that will be used for the
signing and the other for the signing event.
AMP-related Mail Log
and Message Tracking
Changes
and Message Tracking
Changes
Prior to this release, if the threat verdict of a file is unknown, the verdict
was shown as “clean” in the mail log and message tracking.
was shown as “clean” in the mail log and message tracking.
After upgrading to this release, if the threat verdict of a file is unknown,
the mail log and message tracking will show the verdict as “unknown.”
the mail log and message tracking will show the verdict as “unknown.”
Graymail Changes
Prior to this release, if a message is graymail and outbreak filter positive,
the actions configured for graymail are not applied after the message is
released from the outbreak quarantine. The safe unsubscribe banner (if
configured) is not added in this scenario.
the actions configured for graymail are not applied after the message is
released from the outbreak quarantine. The safe unsubscribe banner (if
configured) is not added in this scenario.
After upgrading to this release, the actions configured for graymail are
applied after the message is released from the outbreak quarantine. The
safe unsubscribe banner (if configured) is added in this scenario.
applied after the message is released from the outbreak quarantine. The
safe unsubscribe banner (if configured) is added in this scenario.