Bug 338763 - On local maildir account, moved to trash messages reappear
Summary: On local maildir account, moved to trash messages reappear
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: commands and actions (show other bugs)
Version: 4.14.0
Platform: Debian unstable Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-09-02 21:38 UTC by David Baron
Modified: 2018-01-31 16:53 UTC (History)
0 users

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 David Baron 2014-09-02 21:38:57 UTC
This is a recurring problem.

On a local maildir account, if I move all messages in a folder to trash, next time I enter that folder, the messages will reappear.

If I delete messages one by one, they will stay deleted.

Oftimes, deleting a message will cause remaining messages to disappear from folder's list. Exiting and re-entering the folder will redisplay them. This may or may not be related, possibly another bug.

Reproducible: Always

Steps to Reproduce:
1. Enter a maildir folder
2. Move all messages to trash
3. Exit and re-enter this folder

Actual Results:  
Messages that had been moved to trash reappear in the folder

Expected Results:  
Messages are moved to trash, folder is empty.
Comment 1 Denis Kurz 2017-06-23 20:00:56 UTC
This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks (5.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 oportunity 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.
Comment 2 Denis Kurz 2018-01-31 16:53:06 UTC
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.