Bug 122836

Summary:	imap inconsistent and data loss after conflict resolution
Product:	[Unmaintained] kmail	Reporter:	fleury
Component:	disconnected IMAP	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	crash	CC:	kde, myriam
Priority:	VHI
Version:	1.13.7
Target Milestone:	---
Platform:	unspecified
OS:	Linux
See Also:	https://launchpad.net/bugs/50039
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description fleury 2006-02-28 13:41:25 UTC

Version:           1.9.1 (using KDE 3.5.1, Gentoo)
Compiler:          gcc version 3.3.5-20050130 (Gentoo 3.3.5.20050130-r1, ssp-3.3.5.20050130-1, pie-8.7.7.1)
OS:                Linux (i686) release 2.6.15-gentoo-r1

I use disconnected IMAP as a resource for calendar and addressbook. It has happened now about 3 times where the imap kioslave gets into 100% cpu, typically after it has noticed a conflict in data even though I have not edited any event/address. This seems also to happen when I update an event, then re-update it before it had a chance to sync with the IMAP server (every 5 minutes or so). Then, it gets into conflict resolution mode, then IMAP trashing.

The result is then:
- some events/contacts are simply lost
- I have 3000+ empty messages in the corresponding folder (Calendar/ Contacts) all saying "No subject" (once I even had 19000+), which makes the syncing then horribly long.
- I have seen no pattern in the remaining data (like only the oldest, only the first half of the addressbook, etc.)

The data seems to be removed from the IMAP server, as I share this calendar/contacts with somebody, and their copy gets updated to the lossy version.

I may do some more operations on this if needed, as we share this on a "test trial" style.

Comment 1 FernandoMiguel 2008-12-04 10:43:40 UTC

Please check https://bugs.launchpad.net/ubuntu/+source/kdepim/+bug/50039

it has a lot of information on this subject, as well as confirmation of yahoo corruption headers, as mention by Ingo on KDEPIM users list

Comment 2 Myriam Schweingruber 2012-07-09 11:04:46 UTC

I can confirm this with the latest kmail1 series, up until now I was not able to reproduce it on kmail2 but since on kmail2 I can't use IMAP at all this is rather difficult.

Could somebody else reproduce this with Kmail2? Changed severity to "Very high" as it involves data loss on the IMAP server

Comment 3 Myriam Schweingruber 2012-08-19 11:04:16 UTC

Thank you for your report. Kmail1 is currently unmaintained and the code has changed sufficiently in Kmail2 so the backtraces are not really useful anymore. Should you experience the same crash in Kmail 4.8.5 or later, please open a new report for Kmail2. Thank you for your understanding