Bug 303284

Summary: Deleted emails return as greyed out and cannot be removed
Product: [Applications] kmail2 Reporter: john
Component: foldersAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED DUPLICATE    
Severity: major CC: ab4bd, reavertm, winter
Priority: NOR    
Version: 4.9.1   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:

Description john 2012-07-10 08:41:21 UTC 
IMAP accounts.
After an email has been deleted it moves to trash folder. On next sync it returns as a greyed out email which cannot be accessed/dealt with in any way.

The waste-bin can be emptied as normal.

Using another email client (evolution), the deleted emails do not show up as greyed out (they don't show up at all in their original folder), but are in the Trash folder. Deleting them here removes the greyed out emails in kMail2.

John

Reproducible: Always

Steps to Reproduce:
1. Delete an email
2. Wait for sync
3. Grey email appears
Actual Results:  
deleted email appears as greyed out in its original folder and cannot be accessed.
Checking the emails on the mail server (courier) the emails are present in the original folder.

Expected Results:  
Email should disappear

Evolution shows the greyed out emails in the Trash folder. Deleting them here removes them from the server, and from kmail2.
Comment 1 john 2012-07-10 16:02:27 UTC 
I have just noticed that this 'greyed out' behaviour occurs when I move emails to another folder - so not just the Trash folder.
Comment 2 George L. Emigh 2012-09-13 18:20:27 UTC 
I'm experiencing this behaviour when I move emails to another folder in an IMAP account, has anyone a workaround to remove the greyed out emails?
Comment 3 George L. Emigh 2012-09-13 18:33:00 UTC 
Sorry, I forgot to mention I'm using: KDE 4.9.1 on Gentoo
Comment 4 Myriam Schweingruber 2012-09-14 16:10:48 UTC 
Setting status to confirmed.
Comment 5 Maciej Mrozowski 2014-06-12 19:57:01 UTC 
This is duplicate of bug 316153.
Comment 6 Allen Winter 2014-06-12 20:03:43 UTC 

*** This bug has been marked as a duplicate of bug 316153 ***