> You can't just yet anyway; you can create a spool file 'folder', but it
> doesn't show up anywhere, and can't be opened from the gui yet; have to
> work something out on how to make this happen (which hopefully isn't the
> same awful hack used for local stores, sigh).
The awful hack for local stores is because the shell does half the
bookkeeping (and Ettore and I are talking about how to fix it.)
For spools and maildirs, you just want to implement
CamelStore::get_folder_info and use the same code paths to create the
storage and fill in the folders as IMAP does.
For a spool file, the folder tree would just be the one folder, I guess.
I think the standard for maildirs is to do:
path/{new,tmp,cur}
path/.foo/{new,tmp,cur}
path/.bar/{new,tmp,cur}
path/.bar/.baz/{new,tmp/cur}
(note the dots) for
path
|-foo
+-bar
+-baz
where "path" is a folder too. This is how Courier imapd sets things up
anyway. (Assuming "path" was ~/Maildir/, it would call the folders
"INBOX", "INBOX.foo", "INBOX.bar", and "INBOX.bar.baz".)
-- Dan
_______________________________________________
evolution-hackers maillist - [EMAIL PROTECTED]
http://lists.helixcode.com/mailman/listinfo/evolution-hackers
