In this situation the goal is to archive automatically all incoming and outgoing messages and to keep track of the changes made to the messages.

This implies that for a configurable amount of time each message exists at least two times in the system; once in the primary store and once in the archive store. The used storage can be reduced by stubbing the messages in the primary store.

In this configuration the zarafa-dagent and zarafa-spooler are also involved to make sure all incoming and outgoing messages get archived.