Cisco Cisco Email Security Appliance C680 Notas de publicación

the Security Management appliance discards the reporting data for those features. 
If the Security Management appliance is running AsyncOS 6.7.0 or 6.7.3, it sends 
an alert once each time the reporting service begins, such as on a reboot, stating 
that the reporting service is receiving data that it cannot process.

Your Security Management appliance must be running AsyncOS 6.7.6 or later in 
order to use centralized reporting for the DLP and Marketing Mail features.

SNMP does not start when you boot the appliance after upgrading to AsyncOS 
7.1.1. Use 

snmpconfig -> setup

 and then 

commit 

to enable it.

For DKIM Authentication, IronPort currently supports version 8 of the Draft 
Specification of ‘Authentication-Results:’ header.

For SPF/SIDF verification, the 

spf-passed

 rule is no longer available in content 

filters. To maintain backwards compatibility, the 

spf-passed

 content filter rule 

will be accepted from XML configuration files but it will be converted to the 

spf-status

 rule with corresponding arguments. 

spf-passed

 will be changed to 

spf-status == "Pass"

 and NOT spf-passed to 

spf-status != "Pass"

. You can, 

however, still use the 

spf-passed

 message filter.

IronPort does not generally support the backward compatibility of configuration 
files with previous major releases. AsyncOS 7.1 does not support configuration 
files from AsyncOS 7.0.1 or earlier. 

When you configure AsyncOS to use received headers, you can specify that the 
header reflects one of the following hostnames:

The hostname of the Virtual Gateway used for delivering the message

The hostname of the interface the message is received on