Applicable to V2 volume format only. This option specifies the maximum number of archive files (.zz) that may be open at any one time. Lower values reduce memory footprint, however negatively impact archiving performance. Higher values increase memory utilization, while increase archiving performance.
Maximum queue size
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.
Whether or not to deduplicate data.
New volume format
Specifies the volume format of all newly created volumes. After applying this setting, it is necessary to create a new volume in Configuration->Volumes to ensure that data is written in the selected format.
Periodically compact volume store data
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.
Applicable to V2 volume format only. Specifies the interval to wait between compound archive file compactions (see above).
Do not archive
items larger than ..
Items greater than the size specified (in megabytes) will be rejected for archiving. The purpose of this setting is to protect against denial of service attacks.
Maximum no. Archiving
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.
Force mail server to retry on archive failure
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).
WORM drive support
Whether or not a WORM drive is being used. In this case, MailArchiva will be sure to write data only once to the store path. The volumeinfo file used to maintain volume status will be stored in the volume index path and not the store path.
Was this information helpful?
Thank you Your feedback helps us to continually improve our content.