Finally we need to agree that IMAPdir is _not_ Maildir++. It's not one-to-one compatible because it supports _more_ than Maildir++ does.
I was thinking about this last night, and I think the current backend code should be left as an option when IMAPdir support is added. I won't care and will happily use IMAPdir, but surely there are people who will want strict courier imap compatibility. I imagine that since the code is designed to have pluggable backends, having a Maildir++ / IMAPdir option shouldn't be too hard.. right?
No, we just need to define what _is_ an IMAPdir entry. And if we use Caskey's escape characters, they all are.
Wow, I had totally missed that message!
-Dan
