There is a bug in the KDE Bugzilla, #104956 [1] which has attracted an 
enormous amount of comments and it has been closed and reopened several 
times. This bug report has become a kind of magnet for *all* cases of mail 
loss (real or perceived) where DIMAP is vaguely involved. The KMail 
developers believe that the *original* bug has been solved -- but not 
necessarily all other issues related to DIMAP. However, because the bug is 
still attracting comments (over 180 comments as of this writing) it is 
horribly confusing. Especially since the bug now contains *several* different 
and unrelated issues (except they all have DIMAP as common factor). At the 
Osnabrueck meeting this weekend the KMail developers and the rest of the KDE 
PIM team talked about the bug and its resolution and came to the following 
conclusion:

- the bug will be closed again.
- people with current issues with DIMAP [2] are asked to open *new* bugs.
- further comments on bug 104956 will be ignored.

This measure has everything to do with keeping the bug system usable for 
developers as well. The bug system is *not* a place for long discussion, and 
this bug has become unmanageable as a result. For instance, the crashes 
reported in comment #161 are best dealt with as a separate issue instead of 
buried in such a long discussion. Those are related to messages being 
deleted "out from under" other KMail parts, not DIMAP loss due to flaky 
internet connection which is what the original bug was and which has been 
fixed. Again: distinct bugs which share only the common factor DIMAP should 
not be bunched together in the bug tracker.

This is being posted to the kde-pim mailing list so that any discussion can 
happen *there*, also in public. We believe in the good will and integrity of 
those people who have commented on the bug and the various other bugs in 
there; we ask that they *continue* to watch over DIMAP bugs, just not this 
one -- because the bug report itself is broken.


[ade], writing on behalf of the KMail and KDE PIM developers (Ingo, Till, 
Cornelius, Will, Volker, Thorsten, Martin, Frank and Tobias, to name a few).


[1] http://bugs.kde.org/show_bug.cgi?id=104956

[2] For instance, you can effectively shoot yourself in the foot with a 
combination of F5 (sync only this folder) and message moving plus destroying 
the local cache. I will illustrate this with an example from SVN to show how 
this foot-shooting works. Suppose you have a SVN checkout with directories a/ 
and b/ and a file f in b/ .

	$ cd b/
	$ svn mv f ../a/

Now f is marked as to-be-deleted in b/ and to-be-added in a/

	$ svn commit -m "Move f"

This commits *only* the delete in b/, because you're in b/. The use of F5 is 
comparable. Now throw away your local changes on a/ :

	$ cd ..
	$ rm -rf a
	$ svn up

*BLAM!*


-- 
KDE Quality Team  http://www.englishbreakfastnetwork.org/
GPG: FEA2 A3FE    http://people.fruitsalad.org/adridg/
_______________________________________________
kde-pim mailing list
kde-pim@kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
kde-pim home page at http://pim.kde.org/