Bug 290353 - kmail loses emails during recursive refresh
Summary: kmail loses emails during recursive refresh
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kontact
Classification: Applications
Component: mail (show other bugs)
Version: 4.7.2
Platform: openSUSE Linux
: NOR major
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-01 23:19 UTC by Bruno Haible
Modified: 2017-01-07 21:33 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 Bruno Haible 2012-01-01 23:19:29 UTC
Version:           4.7.2 (using KDE 4.7.3) 
OS:                Linux

In kmail 4.7.4. Using a old kmail-formatted maildir (mixedmaildir).

In the folders tree, I selected a folder with many subfolders and pressed
Ctrl-F5 (recursive refresh). There was no visible sign of progress (probably
because the medium is a slow USB 1.1 disk). I pressed Ctrl-F5 (recursive refresh)
again. Then, after a long processing time, I found that in some (few) folders
some mails have been removed (compared to a backup a made just before the
operation).


Reproducible: Didn't try

Steps to Reproduce:
Press Ctrl-F5 two or more times on a folder (in a mixedmaildir resource)
with many subfolders.

Actual Results:  
Some of the mailbox files are modified: some mails are simply deleted.
In some case it were 1-3 mails at the end of the mailbox file; in other cases
apparently random mails inside the mailbox file.


Expected Results:  
None of the mailbox files (.mbox format) gets modified by the operation.
Comment 1 Denis Kurz 2016-09-24 19:26:44 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kontact (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 2 Denis Kurz 2017-01-07 21:33:07 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.