Compliance Archiving Theory of Operations

The figure below shows a low level view of a compliance architecture.

Figure 2 Low-Level Architectural View of the Sun Compliance and Content Management Solution /Messaging Server Compliance Archiving

As shown in the figure, messages to be archived are copied from the MTA relay to a staging folder where messages are moved into the Sun Compliance and Content Management Solution at regular intervals. Archiving can be set to occur either before or after spam and virus filtering.

An AXS-One library file called libarch.so is used to implement the archiving functionality on the messaging server side. The archive stream, that is, the messages to be archived, is controlled by the Messaging Server spam filter interface. Messages can be archived on a per user, domain, channel, or per system basis (see Specifying the Messages to Be Filtered in Sun Java System Messaging Server 6.3 Administration Guide.

The arrow pointing from the IMAP Append function to the staging directory indicates messages that are moved or copied from a non-archive folder to an archive folder are archived. This is, any new message arriving into the archived part of the system is archived.