Chapter 6. Further Info
In the next section of this manual, you will find a list of links that has been of much help to me when writing this manual. First let us have a look at a useful feature of KMail in Kolab mode which will be of great help if you experience some synchronization problems between the Kolab server and the Kolab client.
6.1. Trouble Shooting
After a system crash or any unexpected event, while your are working with KMail, the user can experience synchronization problems and eventually the KDE Kolab client could crash when synchronizing to the Kolab server. This comes from the fact that the total mail count is higher than what it actually is in the folders.
Other cases of folders corruption: The user has stored some data in a read only folder. For example in a shared folder that has been configured as read only by its owner or any of the 'account names' folders (e-g upon the INBOX folder of our Kolab account or in the user folder of a shared folder as shown in our example).
The first thing to do in case of IMAP synchronization problems is to check if no data has been put in the wrong folders and eventually to move this data. You should then be able to synchronize with the Kolab server.
Next step would be to use the Refresh Local IMAP Cache function of KMail in Kolab mode which has been implemented to delete the local cache and download everything from the Kolab server again, eliminating the cause of the troubles.
To reach this new feature, point to the File->Refresh Local IMAP Cache option of KMail in Kolab mode, you will be prompted to confirm your choice.
Click on the Refresh button to execute the operation and re-synchronize your folders.