AsyncOS 5.5.1-014 for Email is now available

Question

UPDATE: 2008-2-26 5.5.1-014 releases:
This release includes a number of fixes:
* Fixed: Appliances Are Not Generating SNMP Traps
* Fixed: Leftover Files Are Deposited in scanning_temp_files Directory
* Fixed: DNS-Related Memory Issues Delay Acceptance of Incoming Mail
UPDATE: 2007-12-17 5.5.1-011, 5.1.2-011, 4.7.2-005 releases:
This release includes a number of updates and fixes:
* Fixed: 35715,38152,38531,38532 Consolidated LDAP fixes
* Fixed: 38506,38527 Certain malformed messages can severely degrade performance
* Fixed: 38274 IronPort Spam Quarantine alias consolidation issues with Active Directory
* Fixed: 38248 Clustered SafeList/BlockList incorrectly prompts for login
About Earlier Builds of AsyncOS for Email
38527 is also present in earlier builds of AsyncOS for Email. Due to the potential severity of this issue we have also patched the earlier versions listed below, customers who are not ready to upgrade to 5.5.1-011 are encouraged to upgrade to one of these builds:
5.1.2-011
4.7.2-005
UPDATE: 2007-11-28 5.5.1-010 releases:
This Hot Patch release contains the following feature and stability fixes
* New: PCI, HIPAA, GLB and SOX dictionaries preloaded for use in content and message filters
* 37711 Logging into the IronPort Spam Quarantine generates error
* Fixed: 37971 LDAP can slow delivery after log subscription update
* Fixed: 37772 LDAP routing host is ignored when the routing address matches the original address
* Fixed: 36408 application fault in smtpauth
IronPort Systems is pleased to announce the release of AsyncOS 5.5.1-010 for Email for all C-Series and X-Series Email Security Appliances. This release includes all of the powerful new tools for integrated Data Loss Prevention and Encryption released in AsyncOS 5.5.0 as well as critical security patches. IronPort recommends all customers to upgrade to 5.5.1.
* New Feature: IronPort PXE Encryption
* Enhanced: Content Scanning capabilities for Data Loss Prevention
* Enhanced: LDAP Capabilities
* New Feature: DKIM Authentication
* New Feature: End-User Safelists and Blocklists
* Enhanced: Reporting
* Enhanced: Web User Interface
* Updated: Brazilian DST
* Fixed: Double-Byte character rendering in IronPort Spam Quarantine
* Fixed: Performance optimization of disabled content filters
* Fixed: Virtual gateway delivery to host with invalid DNS entry may disrupt mailflow
NOTE: For customers running pre 5.5.0 releases, there is no requirement to upgrade to 5.5.0 first. If 5.5.1 appears as an available upgrade customers are encouraged to upgrade directly to 5.5.1.
Customers running older builds who are not ready to move to 5.5.1, are encouraged to upgrade to our current patched builds:
- 5.1.2-014
These builds provide out latest stability fixes.
Webinar for Selected New 5.5.0 Features
We are pleased to offer a webinar that presents information about Safelist/Blocklists, Smart Identifiers and DKIM. You can download the webinar from the Support Portal:
http://tinyurl.com/2o28uw
Preparing to Upgrade
As a best practice, IronPort recommends preparing for an upgrade by taking the following steps:
1. Save the XML configuration file off of the appliance.
2. Suspend the listeners.
3. Drain the mail queue and the delivery queue.
4. Re-enable the listeners after you upgrade.

Answer 1

I haven't upgraded to 5.5.0 yet, but I was very excited to learn about end-user whitelists and blacklists, which is something we'd been pushing for since we bought our Ironports. Unfortunately, it looks like it's being implemented in a way that makes it impossible for me to deploy at this time.
We have two C350s, and would need the whitelists and blacklists to appear on each box. It appears that I could do this by exporting the database from one machine, transferring it to the other, and then importing it. However, this appears to ONLY be able to be done via the GUI.
This is a showstopper for me, because I do not want to have to log into the Ironport every day to import and export the databases - I would want to automate it. I talked to technical support, and it appears that there is no way to do this via the CLI.
My feature request is this: please consider adding a command that would allow me to remotely force the database to be dumped, and another command to import the database.
Ideally, it would be something like:
safelistconfig dump
safelistconfig import
If that was available, I would make my users a lot happier with this feature.