If you are able to view some emails, but not others, please refer to the article below on "encryption parameters incorrect". If you are not able to see any mails, this fix is most likely to be the problem.
To achieve significant gains in search performance, Архива switched to using numerics for indexing and search. Thus, newer versions of the Архива software use a different index format.
Архива v2.1 is unable to search across indexes created by earlier versions of the product (including the Open Source Edition). Thus, when upgrading from Архива to v2.1 or higher from v2.0 or lower (including OSE), all volumes must be reindexed otherwise no emails will be returned in the search results.
When reindexing volume data, sometimes Архива has difficulty deleting your old indexes. To help it along, it recommended to stop the server, manually delete the contents of the affected index directories, start the server, and reindex the affected volumes.
If there are missing or no emails in your search results, some of your configured volumes may be using different encryption parameters. The Архива system requires that all configured volumes are encrypted using the same encryption algorithm, salt and password. Your server.conf file contains values for the encryption algorithm (security.pbealgorithm), salt (security.salt) and password (security.passhrase).
If these values do not correspond with the values that were used to encrypt any of your previous volume data with, then your Архива system will be unable to return search results. Thus, if you reindex your volumes or attempt to search for emails in the affected volumes, nothing will appear. Most likely, you will also receive errors such as "not in GZIP format" in the debug.log file.
Discrepencies in encryption parameters can arise:
(a) If you upgraded to the (which uses 3DES) from some older versions of the Open Source Edition (which uses DES) or
(b) When moving your Архива system to another server, a different password was chosen in the new system.
To solve the problem, you need to "normalize" all your volume data, such that all volumes are encrypted using the same encryption algorithm, salt and password. To accomplish this, you merely need to run a utility called reencrypt in the mailarchiva_utilities package. The reencrypt utility will attempt to convert the emails in a given volume from one set of encryption parameters to another set of encryption parameters. For instance, it will convert volumes whose emails are encrypted using DES to 3DES, or from one password to another.
In most cases, you do not need to worry about the salt value, as it is set the same across all installations. We use the same salt value by default to protect against total data loss in the event that the server.conf file is accidentally deleted. In this case, to recover your data you merely need to know the password that was used to encrypt your volume data.
If you have forgotten your password, but have you server.conf, it is still possible to recover your data by searching for the value of security.passprase in server.conf and specifying the -pe option when running the reencrypt utility and not the usual -p option for password.
When opening a message, usually if its an decryption issue, you will get an error in the mailarchiva_debug.log saying "not in GZIP format" or something equivalent
Problem: The data in the volume was encrypted using different encryption parameters. For example, the Open Source Edition supports the encryption of data using the DES algorithm, while the by default supports triple-DES (greater security).
Solution: You need to normalize the encryption parameters on your volume. Try this:
Note: it is entirely plausible, that the password and destination password can be the same value. In this case, the reencrypt function will change the encryption parameters (e.g. from DES to 3DES)
If you get 'Failed to retrieve the requested message..." when clicking on a message, you might find:
To solve 2) edit a file called "volumeinfo" in the store directory of each volume and make sure that each volume id is unique. if they are not change one character in the id of an overlapping volume and click the reindex button on that volume in the configuration screen.