ZCS Administrator Guide 8.0
ZCS Administrator Guide 8.0
Network Edition


Archiving and Discovery > How Archiving Works

How Archiving Works
When a message is sent or received by a user, the message is always routed through the Postfix MTA. The Postfix MTA allows integrating software that can perform actions on messages that are in flight. When archiving is enabled for the sender or the recipient of messages, Zimbra Archiving integrates with an MTA hook and the Amavisd-New utility to fork a copy of the message.
The “does recipient or sender have archiving enabled” check is performed on the SMTP standard envelope and not on the From or To/Cc headers. Since checks are performed on the envelope, Bcc copies and messages sent to distribution lists are captured.
For example, if User A sends a message to User B, and if User B has archiving enabled, the MTA delivers two messages — one to User B’s mailbox and one to User B’s archive mailbox. The message received in User B’s mailbox looks normal, as shown in the following example:
 
The message received in User B’s archive mailbox contains additional X-Envelope-From and X-Envelope-To headers. These headers show the real email address the message was sent from and each of the email addresses that the message was sent to.
 
Zimbra archiving can be set up to create archiving accounts that are maintained within ZCS or to work with third-party archiving systems using SMTP forwarding to send messages to a third-party archive server. For third-party archiving, ZCS is configured to act as the forwarding agent.
Copyright © 2012 VMware Inc.