Cisco Cisco Email Security Appliance C670

71565

When you import a configuration file from a system running on a different hardware 
platform, there is a possibility to incorrectly configure the disk management so that 
the Email Security appliance is configured to use more space than is available

76201

If your Email Security appliance is connected to a Security Management appliance, 
reverting the version of AsyncOS on the ESA to a previous version prevents the SMA 
from communicating with it.

Workaround: Re-authenticate the SMA’s connection to the ESA.

75046

AsyncOS for Email may not sign outgoing messages using DKIM if the appliance 
uses a Virtual Gateway hostname in the received header. The C300D, C350D, C360D, 
and C370D appliances use a Virtual Gateway hostname in the received header by 
default. Cisco recommends using the hostname of the interface that received the 
message in the received header to guarantee that the appliance signs messages using 
DKIM.

76940

Using IronPort Mail Merge (IPMM) variables for outgoing messages may invalidate 
the DKIM signature for any signed messages that are altered by IPMM. IPMM is only 
used on C300D, C350D, C360D, and C370D appliances. 

77059

AsyncOS sometimes cleans bare CR and LF characters from messages, which results 
in Sophos flagging the messages as unscannable.

77609

Neither the 

who

 CLI command nor the Active Sessions page in the GUI can identify 

active CLI users with usernames 16 characters or longer.