Summary:

EMF Policy Archive Options explained.

Detailed Information:

Original: A copy of the original message as received by EMF is archived.

Decomposed: Copy of the message after EMF has "decomposed" it. For encrypted messages, a plain text copy will be archived. For plain text messages, this option is same as "archive original".

Processed: The message as forwarded by EMF is archived. Note that multiple copies of the same message can be archived. This will happen when the message gets partitioned due to recipient specific policies (e.g., you add different annotations for different recipients).

Archiving and SPN:

Original: The archived message can be encrypted (e.g., when the encrypted message is received from another SPN domain) or plain text (e.g., from an internal sender for a recipient in another SPN domain).

Decomposed: A plain text copy of the decomposed message is archived.

Processed: An encrypted or plain text copy of the message is archived depending on whether EMF forwarded the message as encrypted or as plain text. For example, when EMF receives an encrypted message from a SPN domain, it will decrypt the message and forward the plain text message to the internal recipient. But when EMF receives a plain text message from an internal sender for a SPN domain, EMF will encrypt the message and forward the encrypted message to the remote SPN domain. For server-to-client and client-to-client encryption, an encrypted message will be archived.

Additional Information:

For additional information on using the EMF archiving feature, see the related article Using the Archive function to troubleshoot problems on the right.