Cisco Cisco Email Security Appliance C370 Release Notes
2
Release Notes for Hot Patch 1 for Cisco IronPort AsyncOS 7.6.1 for Email Security
Resolved Issues
Resolved Issues
The following issues are resolved in this release:
Additional Information
For additional information about Cisco IronPort AsyncOS 7.6.1 for Email Security, see the Release
Notes at
Notes at
.
Service and Support
You can request our support by phone, email, or online 24 hours a day, 7 days a week.
During customer support hours (24 hours per day, Monday through Friday excluding U.S. holidays), an
engineer will contact you within an hour of your request.
engineer will contact you within an hour of your request.
Table 1
Resolved Issues in this release of AsyncOS for Email Security
Defect ID
Description
81090
AsyncOS 7.6.1 for Email Hot Patch Includes Expired Version of Sophos
Anti-Virus
Anti-Virus
The version of Sophos Anti-Virus included in this hot patch release has expired. You
will receive an alert notifying you of the expired version after you upgrade your
appliance to this build.
will receive an alert notifying you of the expired version after you upgrade your
appliance to this build.
The appliance will automatically download the latest version of Sophos Anti-Virus
from the upgrade server after the upgrade is complete. There will be little to no impact
on anti-virus scanning performance.
from the upgrade server after the upgrade is complete. There will be little to no impact
on anti-virus scanning performance.
86322
Fixed: AsyncOS 7.6.1 Does Not Allow 169.254.0.0/16 Addresses for Destination
Domains
Domains
The
169.254.0.0/16
IP address block is reserved for link-local addressing in IPv4;
however, this address block can be used by organizations on isolated networks.
Previous versions of AsyncOS 7.6 considered these IP addresses to be invalid and did
not route messages to mail gateways with these addresses. It would return error
message saying that the domain’s MX records were invalid.
Previous versions of AsyncOS 7.6 considered these IP addresses to be invalid and did
not route messages to mail gateways with these addresses. It would return error
message saying that the domain’s MX records were invalid.
This issue has been resolved. The Email Security appliance will now route messages
to gateways that have an IP address from this block.
to gateways that have an IP address from this block.
77819
Fixed: SMTP Route for Top Level Domain Ignored Due to Partial Subdomain
Entry
Entry
Previously, the Email Security appliance would not route a message to the SMTP
route defined for a top level domain if there was another SMTP route entry for a
partial domain that had the same top level domain. The appliance would instead use
the default route or use MX for sending the messageThe appliance would instead use
the default route or use MX for sending the message. For example, the appliance
would not send an email message for
route defined for a top level domain if there was another SMTP route entry for a
partial domain that had the same top level domain. The appliance would instead use
the default route or use MX for sending the messageThe appliance would instead use
the default route or use MX for sending the message. For example, the appliance
would not send an email message for
joe@example.co.jp
to the SMTP route defined
for the top level domain
.jp
if there was an SMTP route entry for
.test.co.jp
, even
though they only share the top level domain. This issue has been resolved.