One of your users reports not seeing any content in their mailbox or missing certain content, despite having the content in their mail store folder on the backend. Within the Webadmin, you review their User and see a smaller mailbox size than expected (for example, seeing 0b of data). You are seeing a large number of Indexing errors within the Server logs for the user, such as the following:
FolderIndexTraitsImpl.cpp: Index error in folder ~firstname.lastname@example.org/Calendar: Cannot parse calendar message file 00000001.eml
From version 7.3.0 and above, Kerio Connect automatically walks through data storage in the background, performing a check of auxiliary files and fixes issues in case of detected corruption. By default, this process will run when the server is restarted or every 6 hours and can often address any indexing issues.
Additionally, administrators can manually trigger the start of the integrity check from the Kerio Connect Administration interface for specific users or public folders.
For Specific Users
- Log in to the Kerio Connect Administration using an administrator account with 'read/write' access rights.
- Navigate to Accounts > Users. A list of users will be displayed, as shown below.
- Choose one or more users.
- Click on More Actions and then click on Reindex Mailbox.
For Public Folders
- In the Kerio Connect Administration, navigate to Configuration > Domains.
- Click Public Folders and then click Reindex Folders.
When the Reindexing is triggered from the WebAdmin, you can review the Config Logs (WebAdmin > Logs > Config) to monitor its progress. Once it completes, you will see an "Integrity check successfully finished" message, as shown above.
Any data consistency issues found during the check are automatically fixed. Any previously missing email items are restored and available within the Webmail. Any previous indexing or corruption-related logging messages are no longer appearing.
If you continue to see indexing errors appearing, this indicates that the automatic Integrity Check failed, and you will need to manually rebuild the index for the affected users.