As reported (elsewhere?) already, there are cases where deleted messages from a GMail account are not actually deleted at all, and remain as "ghosts", greyed-out entries in kmail's message list that cannot be selected. I just discovered that this also happens with entries in the Drafts folder, after sending them. Reproducible: Always Steps to Reproduce: 1. configure a gmail account with the corresponding draft and wastebin ("Bin") folders 2a. write and send a message 3a. delete any message from the active folder *before* having received the notification that the message from (2) was sent successfully OR 2b. compose a message, save it to the Drafts folder 3b. double-click to open it, and then send it. 4. select another folder, and then re-select the previous folder (this may need to be done a few times) Actual Results: The message deleted under 3a. or sent under 3b. will reappear in the list, but ghosted. It can no longer be selected. Expected Results: The message is supposed to have been deleted, so it should not reappear. - this also applies to selections of multiple messages, in the 4.13 and 4.14 series on both Linux and OS X - checking via GMail's web interface or a different client, the ghost messages are indeed not deleted at all - The effect of 3a. can be undone (*before* selecting another folder) by hitting undo (^Z), waiting for the message to reappear as "not deleted", and then deleting it again. After any message sending has completed of course. - The effect can also be undone in akonadiconsole: 1. go to the folder in the browser tab 2. select the message: its attributes will show "/DELETED" 3. right-click the message, and *move* it to the account's Bin folder Cleanup is a major feature IMHO, hence the Major severity I assigned to this ticket.
It happens to me in kmail 5.0.3 whenever some filter moves an email from an IMAP (any IMAP folder, not just gmail) folder to another.
This bug has never been confirmed for a Kontact version that is based on KDE Frameworks, except possibly a Technology Preview version 5.0.x. Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the opportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it. Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12, preferably more recent), please open a new one unless it already exists. Thank you for all your input.