Specifies the size of the receive queue.  Reducing the size of the receive (in Configuration->General->Archive) and index (specified in Configuration->General->Index) queues, limit the total amount of space that the queues may consume on disk. When importing / archiving data, data is temporarily cached on disk until either the archive or index queue is full, at which time, if importing, the import operation will block; while if archiving via SMTP, the operation may result in MailArchiva's inbuilt SMTP server returning a retry later error code such as 421, or 451. Given that, the speed of reading source data is typically faster than speed of encryption, compression + write, especially, with regards to import, it is crucial to set an appropriate queue size taking into account the amount of disk space available on the queue partition such that all available disk space cannot be consumed during an import operation.

Applicable to V2 volume format only. When using a compound archive file format (i.e. V2), archive files must be rewritten to free up disk space. Since rewriting compound archive files is an expensive operation, it is done on a periodic basis. This option, when enabled, will cause MailArchiva to rewrite compound archive files periodically (i.e. between a defined interval), thus freeing up disk space.

Do not archive
items larger than ..

A higher thread count may increase the archiving performance of the server (up to a limit) by taking advantage of the parallelism of multicore processors and using more available storage IOPS.

On failure to archive data due to insufficient disk space or for a multitude of other reasons, with this option enabled, MailArchiva's inbuilt SMTP server will return a retry later error code such as 421, or 451.

The search interface has the ability to present email threads in an hierarchical manner such that users have the ability to view related emails in a conversation. The process of linking related emails requires MailArchiva to perform post processing of email data. During this post processing step, data is read from the storage, and linked with other related data using a complex statistical algorithm.  Since the post processing step requires constant retrieval of data from storage, it is not recommended to enable this option when volume format is set to V2 or in environments with high traffic flow (for example, >20k mailboxes).