Bug 131860 - New mail gets dropped after upgrade from 3.5.2 to 3.5.3
Summary: New mail gets dropped after upgrade from 3.5.2 to 3.5.3
Status: RESOLVED WAITINGFORINFO
Alias: None
Product: kmail
Classification: Unmaintained
Component: IMAP (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-08-04 14:58 UTC by Ing. Ger Apeldoorn
Modified: 2012-06-08 12:26 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ing. Ger Apeldoorn 2006-08-04 14:58:45 UTC
Version:            (using KDE KDE 3.5.3)
Installed from:    Ubuntu Packages
OS:                Linux

My system:
Ubuntu 6.10 LTS

My Server:
Kolab 2.0.3

I've done an upgrade to KDE 3.5.3 using this repository:
deb ftp://bolugftp.uni-bonn.de/pub/kde/stable/3.5.3/kubuntu dapper main

I've got Sieve Scripts that sort my email on the server. 

Since the upgrade, any mail that was not sorted by the Sieve Script (e.g. whose destination was the INBOX folder) was deleted by Kmail. It took a few days to realize that I was missing mails, because the other (sorted into different folders) mails kept on coming.

The index in KMail was corrupt, so I rebuild the index and refreshed the 
cache. (right-click account->fix problems with IMAP cache->recreate index & 
flush buffer (click both serially)(Translated, actual titles may vary))

Now all is well, except for the missing mails.

Expected behaviour: When the index is corrupt, anything but removing the email should happen. Crash, error, auto-reindex.

Thanks for your efforts for KDE/Kontact/Kmail!

Ger.
Comment 1 Bernhard Janetzki 2006-08-04 16:55:56 UTC
Exactly the same problem for me.
My System:

Ubuntu 6.06 LTS
Kolab 2.0.3
KDE: 3.5.4
Im using Sieve Scripts too.
Comment 2 Jeroen van Meeuwen (Kolab Systems) 2012-06-08 12:26:20 UTC
Please be so kind as to verify whether this issue still exists with KDE 4.8, and reopen this ticket if necessary.