Version: (using KDE KDE 3.5.4) Installed from: Debian testing/unstable Packages The whole purpose of IMAP is to be able to handle the same mail account from different locations. So, having mails deleted remotely is a common situation. dIMAP now gives a warning for each folder where it had happened, which is very annoying when you have more than 10 mailing list folders (think "message expiration") Moreover, the warning lists the UIDs of the messages, which, frankly, is not that useful to determine if the deleted messages where important or not. It would have least be a great thing to be able to disable this warning (for instance by a "don't show this message again" checkbox).
I have to agree. It is really annoying when emails are deleted and this message is shown,which happens quite often when you share folders! Please add an option to disable these warnings.
Yes, this is very annoying. I have a cron job on my server which removes old mails form my mailing list folders every night, so every morning I get this dialog several times every morning.
It looks like this is caused by a patch applied by gentoo (and, looking at the platform for this bug, I guess debian too).
Well, I looked at it and saw a SVN commit in KDE's svn (so, no, not a gentoo patch). It seems that it was to track down problems with KMail deleting mails that were *not* deleted. I don't know how only having the mail numbers would help tracking that down, but nonetheless ... It seems that it was removed in KDE 3.5 (I don't have those warnings). If somebody can confirm that for me, I'll close the bug
For me it started showing up with the latest gentoo package (3.5.5-r2), which added the kmail-3.5.5-dimap-mail-loss.patch. This patch contains the warning, so I guess gentoo decided to put the removed code back in there.
As far as I can see the problem is due to the #define MAIL_LOSS_DEBUGGING 0 at the beginning of the patch. I assume the patch author wanted to disable debugging output when releasing the patch. However, gcc only reads #define MAIL_LOSS_DEBUGGING ignoring the 0 and includes all code between #ifdef MAIL_LOSS_DEBUGGING and #endif. A simple solution to this bug is to comment (or remove) the line #define MAIL_LOSS_DEBUGGING 0 which was most probably the behaviour originally intended.
Gentoo users, see: http://bugs.gentoo.org/show_bug.cgi?id=157049
*** Bug 138855 has been marked as a duplicate of this bug. ***
This works for me in KDE 4.3