You can use also a integration schemes like Cisco IronPort (MX position) - Exim (simple real time backup and advance route driver) - Zimbra (end user agent).
Zimbra and IronPort integration (single and bundle solutions) is simple and can be implemented in two good ways. Ironport works like simple mailgateway and can route (route section) a messages wherever you show (configure) for each of your internal domain - Manfred Zhu described it in the above post . Zimbra can also route to external smtp server all messages (external and internal Zimbra messages too). It's very importnat, because, if you use a IronPort e-mail encryption feature (RES) for internal and external users you cann add to your Zimbra config external smtp server (GUI: Global settings - MTA - Network, Mta for external route). Do not forget to Zimbra mail to route the internal interface of the IronPort. You must define in Zimbra GUI a internal (inside) IP/hostname to IronPort service.
But I prefer Zimbra integration with IronPort and exim, because the exim has more powerful in my ability to control the messages, than in the Zimbra postfix. But if you want, you don't need use exim solution!
Simple way is use a Zimbra like a classic webmail (colaborate) and pop/imap server and IronPort like incomming and outgoing smtp server (IronPort can be external and internal smtp server, with support auth internal users with any ldap to send e-mails). In my opinion this way is not sufficiently secure.
Simple route with Zimbra, IronPort (your MX) and Exim (exim can backup all incomming and outgoing messages, it's easy and free):
(incomming external message from outside users) -> IronPort -> Exim (live backup solution) -> Zimbra (local user).
(outgoing internal message to outside users) Zimbra (local user) -> Exim -> Ironport -> external user
(outgoing internal message to internal users) Zimbra (local user)-> Exim -> Ironport -> Exim -> Zimbra (local user) or Zimbra (local user)->Exim ->Ironport ->Zimbra (local user)
To identify and authenticate your internal users for IronPort and Zimbra, you can use the Zimbra (Open) ldap or external ldap server, like OpenLdap / Sun One Directory. - It's depends on your model solutions.
QUARANTINE:
Basic problem with IronPort Spam messages and Zimbra (Unify your SYSTEM Spam quarantine, without IronPort quarantine store):
Global filters for all users..
Best way: Disable your SPAM quarantine in IronPort and tag (define header or subject like [**SPAM**] or [**SUSPECTED SPAM**] ) all spam messages and suspected messages with deliver options. Zimbra users can add a system filters in zimbra client and store SPAM messages in local Zimbra folders. I don't know yet how to set the global system filters configuration of the Zimbra.
If you don't want disable a IronPort SPAM quarantine, you can also configure the IronPort in such a way as to send e-mails with links to spam messages to your internal users (eg. once a hour / day / week).