Distributed James Server — deletedMessageVault.properties

Deleted Messages Vault is the component in charge of retaining messages before they are going to be deleted. Messages stored in the Deleted Messages Vault could be deleted after exceeding their retentionPeriod (explained below). It also supports to restore or export messages matching with defined criteria in WebAdmin deleted messages vault document by using WebAdmin endpoints.

Deleted Messages Vault Configuration

To make James use DeletedMessageVault, you need to configure the PreDeletionHook for it.

How to do this is documented in the listeners.xml Mailbox Listener Configuration page.

The Deleted Messages Vault also stores and manages deleted messages into a BlobStore. The BlobStore can be either based on an object storage or on Cassandra. For configuring the BlobStore the vault will use, you can look at blobstore.properties BlobStore Configuration section.

deletedMessageVault.properties

Consult this example to get some examples and hints.

Table 1. deletedMessageVault.properties content
Property name explanation

retentionPeriod

Deleted messages stored in the Deleted Messages Vault are expired after this period (default: 1 year). It can be expressed in y years, d days, h hours, …​