Bug 322697

Summary: Copying (or moving) a large number of emails results in empty maildir files
Product: [Applications] kmail2 Reporter: Long time KDE user <morekdebugs>
Component: commands and actionsAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED UNMAINTAINED    
Severity: critical    
Priority: NOR    
Version: 4.10.5   
Target Milestone: ---   
Platform: Kubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Long time KDE user 2013-07-22 16:00:53 UTC 
I am attempting to move a large number (c 27000) of emails into folders.

The emails are from a backup and have been restored to a single folder.

When I copy them from the backup folder, approximately 80% end up zero length and examining the maildir folder shows them to be 1 byte long.

This may also explain why I am having to do a restore, as I originally had a large number of emails that appeared correctly in the akonadi database, but were not actually in the maildir and appeared empty when I tried to look at the contents.

I am unable to restore old emails into kmail and will have to use another client until this is fixed.






Reproducible: Always

Steps to Reproduce:
1.  Import a large number of emails from a backup of a maildir folder
2.  Attempt to copy emails to existing inbox or folder structure

Actual Results:  
Kmail reports the copy is successful but examining the kmail directory shows many files of 1B - once the folder is refreshed these show up as Subject:(No Subject) Sender:Unknown

Expected Results:  
All emails copied with the content intact.
Comment 1 Denis Kurz 2016-09-24 17:54:34 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 kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.
Comment 2 Denis Kurz 2017-01-07 21:44:39 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.