Update - 2009-09-29
Based on your feedback, we are delaying the maintenance start time to 15:00 PST (22:00 UTC). The duration remains 6 hours and the day is still October 10th, 2009.
Cisco Systems is pleased to announce a major upgrade of the Cisco Registered Envelope Service (CRES) scheduled for October 10th, 2009. The service will be temporarily unavailable during the upgrade, more information on the maintenance window is available https://www.ironportnation.com/forums/viewtopic.php?t=1483.
This upgrade contains a variety of features and fixes:
New Feature: Automated TLS configuration for Secure Reply
Cisco Registered Envelope Service administrators now have the ability to test and request for provisioning domains for TLS Secure Reply via the UI. Previously, this action required direct Customer Support interaction.
New Feature: PXE Sender Registration
PXE Secure Envelope senders can be configured to receive a welcome email inviting them to sign-up to the CRES User Portal for the purpose of managing their sent Secure Envelopes.
New Feature TLS fall back mechanism
Customers who opt for TLS Secure Reply can now configure their accounts to "fall back" to "Registered Envelope Delivery" if the SMTP-TLS connection fails. This will be the default configuration going forward. Existing customers will need to change their configuration if they want to take advantage of this feature.
New Feature: Progress Bar for file downloads in JavaScript restricted environments
If a recipient's browser disallows JavaScript and the recipient downloads a file, the download progress is indicated by a progress bar.
Fixed: Error Adding Image Via Admin GUI
Fixed: “Forget Me on This Computer” Not Working
Fixed: User Transaction Report Not Working
Fixed: Error Message Missing When Cookies Not Enabled
Fixed: Using a BlackBerry and a Webmail Provider (Gmail, Yahoo!, etc.)
New IP ranges:
As part of this upgrade, we will be moving our outbound email servers to a new set of IP addresses. Customers who have TLS require set up by IP range or firewall rules specific to res.cisco.com will need to modify their infrastructure to accommodate the new IP ranges.
208.90.57/26
204.15.81/26
216.206.186.129/25 *
These ranges can also be queried using our published SPF record.
$ dig +short res.cisco.com txt
"v=spf1 ip4:204.15.81.0/26 ip4:216.206.186.129/25 ip4:208.90.57.0/26 mx:res.cisco.com ~all"
As a best practice we recommend using the hostname rather than IP range to configure TLS. For more information see Knowledge Base article 1442 http://preview.tinyurl.com/l2nbv7
* This is the original CRES ip range. During this migration we recommend you support all three sets of IP ranges.
