Bug 166077 - IMAP messages lost after trying to move them
Summary: IMAP messages lost after trying to move them
Status: RESOLVED NOT A BUG
Alias: None
Product: kmail
Classification: Applications
Component: IMAP (show other bugs)
Version: 1.10.0
Platform: Compiled Sources Linux
: VHI grave
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-07-08 19:41 UTC by Thomas McGuire
Modified: 2008-07-09 01:00 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas McGuire 2008-07-08 19:41:04 UTC
Version:           1.10.0 (using Devel)
Installed from:    Compiled sources
OS:                Linux

Under some circumstances, messages get lost when moving them to IMAP folders.
Steps to reproduce (starting with a fresh config).

1. Add an online IMAP account (I used my googlemail account)
2. Make sure you have to empty folders, A and B, under the root folder
3. Create a dummy filter, so that the action scheduler is activated.
   I used: Size in bytes is less than 0 bytes -> move into folder B
4. Create a draft message with subject "AAA test" or something like that
5. Copy that message from the drafts folder to folder A
6. Move that message from folder B to the IMAP inbox

Result: The message briefly appears in the IMAP inbox, but then vanishes into /dev/null => message lost
Comment 1 Thomas McGuire 2008-07-08 20:18:26 UTC
Typo in step 6, that should be:

6. Move that message from folder A to the IMAP inbox 
Comment 2 Thomas McGuire 2008-07-08 21:06:39 UTC
Some more info:

There is one last step:
7) Click on the IMAP inbox and watch the message disappear

This bug only seems to happen with GMail accounts, Kolab Cryus server doesn't trigger this problem.
This problem also doesn't happen when the filter modifies the mail, for example by rewriting the subject (I tried a filter which changes AAA into BBB).
Comment 3 Thomas McGuire 2008-07-08 21:15:46 UTC
Problem is on Google's side, they simply don't allow duplicate message, but the action scheduler relies on that.
Need to find a workaround.
Comment 4 Thomas McGuire 2008-07-09 01:00:42 UTC
Sorry, it turned out that this bug report is not true and that I fixed the dataloss in r816901 (http://websvn.kde.org/?view=rev&revision=816901).
I could only reproduce it because I had local modifications to the code to track the cause of the bug down...

Filtering with GMail will now simply not work in certain cases, but doesn't cause dataloss.

Sorry for the false alarm.