There are four components to the MPP Email Archive Architecture:

Archive Agents Agents send email into the archive system. An agent can be a journaling email server, an IMAP server, MPP on a supported MTA or MPP Manager when importing. Simply put, Archive Agents send email to the Message Processor. Journaling sources can include MS Exchange 03 or 07, Zarafa, Postfix, Zimbra, CommuniGate Pro, Postfix or more. MPP Manager can import email from over 20 different formats. MPP can be installed as an archive agent on a supported MTA like Postfix or CGP. When this is done MPP has a special protocol to send messages to a central MPP for processing.

Message Processor The Message Processor (MPP) decodes journal reports, processes messages according to your policies and stores in the database. MPP is the message processor. The MPP Virtual Appliance has all components pre-configured as a Message Processor for journal reports.

Message Store The Message Store is where archived messages are actually stored. This is usually a NAS device or large disk array. The Message Store must be accessible by the Message Processor.

Access Server The Access Server provides web access to the email archives. MPP Manager has an embedded web server and provides this service, though MPP Manager can also be run under Apache if desired. The access server must be configured for full text search as README.sphinx