21 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Enhanced Maildir ...
FromSent OnAttachments
Marc HaberJan 9, 2001 4:43 am 
Kris KelleyJan 9, 2001 9:14 am 
Georg LutzJan 9, 2001 2:20 pm 
Chris GreenJan 10, 2001 12:37 am 
Georg LutzJan 10, 2001 1:49 pm 
Marc HaberJan 12, 2001 9:34 am 
Marc HaberJan 12, 2001 9:36 am 
Chris MeadorsJan 12, 2001 10:07 am 
Georg LutzJan 13, 2001 6:10 am 
Georg LutzJan 13, 2001 6:46 am 
Marc HaberJan 13, 2001 1:45 pm 
jhen...@bogon.comJan 14, 2001 12:00 pm 
Mirko ZeibigJan 14, 2001 2:21 pm 
Patrick PriceJan 14, 2001 3:17 pm 
Patrick PriceJan 14, 2001 5:51 pm 
Cindy SmithJan 14, 2001 6:26 pm 
Patrick PriceJan 14, 2001 8:26 pm 
Patrick PriceJan 14, 2001 8:37 pm 
Marc HaberJan 15, 2001 12:11 am 
Marc HaberJan 22, 2001 2:47 am 
Marc HaberJan 22, 2001 2:48 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [courier-users] Enhanced Maildir Specification where?Actions...
From:Kris Kelley (kkel@genericapp.com)
Date:Jan 9, 2001 9:14:22 am
List:net.sourceforge.lists.courier-users

Since the search engines don't show anything when I search for "enhanced maildir" (bringing up only references to maildirmake's man page), I have to ask here. Is the "enhanced maildir" a standard, which software besides courier supports it?

http://www.inter7.com/courierimap/README.maildirquota.html contains an explanation of how the enhanced maildir standard, or "Maildir++", differs from the original maildir standard. The Courier IMAP homepage mentions that SqWebMail and maildrop also support Maildir++.

Any program that supports Maildir will be able to access directories created by Courier. Programs that use the original Maildir standard will not be able to take advantage of Maildir++ features like multiple folders and subfolders, but messages delivered by the Courier server will still be accessible.

I haven't used mutt, so I may be off-base, but if it conforms to the original Maildir standard, then you shouldn't have any problems. The only inconvenience would be you that you can't access email in folders you created using your IMAP client. Now if the makers of mutt came up with their own way of doing subfolders that doesn't conform to Maildir++, then you're going to have incompatability issues, in that mail moved by mutt can't be read by your IMAP client, and vice versa.

The requirements to - have all folders below inbox...

Because of the way Maildir++ defines its heirarchy, and because of the way Courier IMAP differentiates between private and shared mail folders, this is really just an illusion. The inbox is the top-level cur directory; all other mail folders are independent of it. If you use an IMAP client that supports the CAPABILITY command (see http://www.inter7.com/courierimap/FAQ.html#namespace), this becomes more obvious.

- have all folders start with a period...

Probably because the period is the heirarchy separator.

- implement subfolders with a file name kludge instead of using the host OS directories...

I believe this was done so that a single directory could be scanned for all relevant mail folders, making it unnecessary to recursively search a directory tree.

My impression is that Courier and its associated programs were designed with remote email services in mind. Even so, it wouldn't be difficult for somebody to come up with a local client that conforms to the Maildir++ standard, just apparently nobody has yet. If this is really an issue for you, your best recourse may be to keep all email in a single folder (cur, the "inbox") that can be read by any Maildir or Maildir++ compatable program.