Bug 303913 - maildir 'new' directories aren't empty
Summary: maildir 'new' directories aren't empty
Status: RESOLVED DUPLICATE of bug 281797
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 4.8.4
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-22 10:16 UTC by mikael.salson
Modified: 2016-09-25 19:29 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description mikael.salson 2012-07-22 10:16:10 UTC
According to Wikipedia : 
“When the mail user agent process finds messages in the new directory it moves them to cur (using rename() - link then unlink strategy may result in having the message duplicated) and appends an informational suffix to the filename before reading them.”

So I understand that I shouldn't see any file in the new directories. However I have a few ones:
$ find ~/.kde/share/apps/kmail/mail/ -type f | grep -c '/new/'
3902

They are not duplicated messages. Meaning that these messages, as far as I can see, are not in the cur/ directory. One of them, for instance, is new/1342795373.R533.basilic:2,S and we can see that the informational suffix has been appended. I can also see this message in kmail and it cannot be distinguished from other messages (in the same folder in kmail) that are stored in the cur/ directory.

I'm definitely not a maildir expert but that seems to be a non-standard behaviour. I'm also wondering if this can explain the following bug I filed several months ago : https://bugs.kde.org/show_bug.cgi?id=289657

Reproducible: Sometimes

Steps to Reproduce:
Most messages are put in cur/ directories. I don't know what prevent some of them to go there!
Comment 1 Thomas Zell 2014-05-07 18:50:38 UTC
This is still happening in 4.13
Comment 2 Denis Kurz 2016-09-24 18:17:40 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 3 Thomas Zell 2016-09-25 19:09:43 UTC
I think this can be closed as a duplicate of Bug 281797
Comment 4 Denis Kurz 2016-09-25 19:29:45 UTC
Thomas, thanks for pointing this out. I think you are right

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