Bug 86304 - maildir directories require new and tmp subdirs; older versions did not
Summary: maildir directories require new and tmp subdirs; older versions did not
Status: RESOLVED DUPLICATE of bug 83209
Alias: None
Product: kmail
Classification: Applications
Component: maildir (show other bugs)
Version: 1.6.2
Platform: RedHat Enterprise Linux Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2004-07-30 19:58 UTC by Alex Jarrett
Modified: 2008-09-14 22:34 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 Alex Jarrett 2004-07-30 19:58:54 UTC
Version:           1.6.2 (using KDE KDE 3.2.2)
Installed from:    RedHat RPMs
OS:                Linux

I recently upgraded to KMail 1.6.2 from 1.4.3.  I have both mbox and maildir files in my ~/Mail directory.  When 1.6.2 was started, none of the maildir directories showed up unless their maildir structure was complete, with all three subdirectories, "new", "tmp" and "cur". Many of the maildir directories only had the "cur" subdirectory.  When I created "tmp" and "new" directories, the folders showed up.  Version 1.4.3 did not require all three subdirectories to exist.

To reproduce: Close KMail. Remove an empty "tmp" or "new" subdirectory from a maildir folder.  Start KMail - the folder will have disappeared.

I'm not sure if an older KMail version actually created maildir directories without the 3 subdirectories, or if it was an even older client I had used before KMail.  But if it was, some ability to automatically create "tmp" and "new" subdirectories rather than just ignoring the folder would be appreciated.

Thanks,
Alex Jarrett
Comment 1 Philip Rodrigues 2006-10-30 23:38:44 UTC
Behaviour on SVN r599765 is as described. Don't know if it's deliberate though.
Comment 2 Thomas McGuire 2007-07-17 14:14:38 UTC
See also bug 83209.
Comment 3 George Kiagiadakis 2008-09-14 15:41:05 UTC

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