[Dovecot] directory names - have to begin with a dot?
Hi there...
Two questions:
(1) Is there an easy way to have Dovecot recognize subdirectories that do not begin with a dot as sub-hierarchies?
(2) Is there a way to have the root folder map to a certain other mbox/maildir? I want a setup like this:
/ -> $HOME/mbox
/INBOX -> /var/spool/<username>
/folder -> $HOME/mail/folder
/folder/foo -> $HOME/mail/folder/foo
/folder/bar -> $HOME/mail/folder/bar
/folder/foo/bar -> $HOME/mail/folder/foo/bar
(Assuming / as a hierarchy separator - that is,
/folder/foo/bar is the IMAP folder 'bar' inside 'foo' inside
'folder')The idea is something resembling and compatible with the default behaviour of elm/pine/mutt/KMail/evolution, so a user can use both those locally and whatever IMAP client remotely in a similiar organisation...
I would love some further documentation regarding the working of Dovecot's folder lookup and how to achieve different IMAP folder organisations with dovecot. I have not yet looked deep enough into the sources to understand where most of the flexibiliy stems.
Cheers, -- Tom
P.S. anyone checked my trivial patch for settings parsing after closing braces?
-- Tom Alsberg - hacker (being the best description fitting this space) Web page: http://www.cs.huji.ac.il/~alsbergt/ DISCLAIMER: The above message does not even necessarily represent what my fingers have typed on the keyboard, save anything further.
On Thu, 2005-08-04 at 13:39 +0300, Tom Alsberg wrote:
Hi there...
Two questions:
(1) Is there an easy way to have Dovecot recognize subdirectories that do not begin with a dot as sub-hierarchies?
That causes namespace colliding which isn't such a good idea. For example Dovecot creates dovecot.* files, so you couldn't create a "dovecot" folder.
(2) Is there a way to have the root folder map to a certain other mbox/maildir? I want a setup like this:
Nope, but it's planned sometimes after v1.0.
I would love some further documentation regarding the working of Dovecot's folder lookup and how to achieve different IMAP folder organisations with dovecot. I have not yet looked deep enough into the sources to understand where most of the flexibiliy stems.
If you want to implement your 2) part, it needs quite a lot of changing to code. Currently maildir is tied to Maildir++ directory layout and mbox to "normal" directory-layout. The mailbox listing/finding code would have to be separated from the actual mailbox handling code to have mixed mbox/maildirs inside one namespace.
On Sun, Aug 07, 2005 at 06:20:24PM +0300, Timo Sirainen wrote:
On Thu, 2005-08-04 at 13:39 +0300, Tom Alsberg wrote:
(1) Is there an easy way to have Dovecot recognize subdirectories that do not begin with a dot as sub-hierarchies?
That causes namespace colliding which isn't such a good idea. For example Dovecot creates dovecot.* files, so you couldn't create a "dovecot" folder.
I realize that - there would be a few names you can't use... Still, I would like to do that...
(2) Is there a way to have the root folder map to a certain other mbox/maildir? I want a setup like this:
Nope, but it's planned sometimes after v1.0.
Cool...
I would love some further documentation regarding the working of Dovecot's folder lookup and how to achieve different IMAP folder organisations with dovecot. I have not yet looked deep enough into the sources to understand where most of the flexibiliy stems.
If you want to implement your 2) part, it needs quite a lot of changing to code.
Why? I wasn't talking in (2) about mixing mbox and maildir... All it requires, it seems, is for mailbox names not to begin with a dot, and to be able to map the IMAP root to a special specific folder...
Currently maildir is tied to Maildir++ directory layout and mbox to "normal" directory-layout. The mailbox listing/finding code would have to be separated from the actual mailbox handling code to have mixed mbox/maildirs inside one namespace.
Yeah, I know that... That's what's blocking the ability to mix mbox and maildir in one tree (we had a discussion once...). I thought you said you have this planned for somewhen after 1.0 as well...
Cheers, -- Tom
-- Tom Alsberg - hacker (being the best description fitting this space) Web page: http://www.cs.huji.ac.il/~alsbergt/ DISCLAIMER: The above message does not even necessarily represent what my fingers have typed on the keyboard, save anything further.
On Sun, 2005-08-07 at 18:58 +0300, Tom Alsberg wrote:
If you want to implement your 2) part, it needs quite a lot of changing to code.
Why? I wasn't talking in (2) about mixing mbox and maildir... All it requires, it seems, is for mailbox names not to begin with a dot, and to be able to map the IMAP root to a special specific folder...
Hmm. I guess I didn't then understand the question. It looked like a mixed mbox/maildir tree. Mapping sounds like namespaces that Dovecot already has:
/ -> $HOME/mbox
/INBOX -> /var/spool/<username>
/folder -> $HOME/mail/folder
/folder/foo -> $HOME/mail/folder/foo
/folder/bar -> $HOME/mail/folder/bar
/folder/foo/bar -> $HOME/mail/folder/foo/barThere can't be a mailbox named "/" (or ""), so the first one couldn't work? The others could probably be done using namespaces? Assuming you're talking about only mboxes here, not maildirs.
On Sun, Aug 07, 2005 at 07:11:55PM +0300, Timo Sirainen wrote:
Hmm. I guess I didn't then understand the question. It looked like a mixed mbox/maildir tree. Mapping sounds like namespaces that Dovecot already has:
/ -> $HOME/mbox /INBOX -> /var/spool/<username> /folder -> $HOME/mail/folder /folder/foo -> $HOME/mail/folder/foo /folder/bar -> $HOME/mail/folder/bar /folder/foo/bar -> $HOME/mail/folder/foo/barThere can't be a mailbox named "/" (or ""), so the first one couldn't work? The others could probably be done using namespaces? Assuming you're talking about only mboxes here, not maildirs.
Actually, in my example, / and /INBOX are mboxes ($HOME/mbox and /var/spool/<username> respectively), while everything in /folder are maildirs. The two wishes I've been trying to demonstrate in this example are: (1) dotless maildirs and subfolders, and (2) mapping the IMAP root folder (I understood there is something like that, that is - IMAP mail folders are a rooted hierarchy) to some specific mbox/maildir.
Cheers, -- Tom
-- Tom Alsberg - hacker (being the best description fitting this space) Web page: http://www.cs.huji.ac.il/~alsbergt/ DISCLAIMER: The above message does not even necessarily represent what my fingers have typed on the keyboard, save anything further.
On Sun, 2005-08-07 at 20:10 +0300, Tom Alsberg wrote:
On Sun, Aug 07, 2005 at 07:11:55PM +0300, Timo Sirainen wrote:
Hmm. I guess I didn't then understand the question. It looked like a mixed mbox/maildir tree. Mapping sounds like namespaces that Dovecot already has:
/ -> $HOME/mbox /INBOX -> /var/spool/<username> /folder -> $HOME/mail/folder /folder/foo -> $HOME/mail/folder/foo /folder/bar -> $HOME/mail/folder/bar /folder/foo/bar -> $HOME/mail/folder/foo/barThere can't be a mailbox named "/" (or ""), so the first one couldn't work? The others could probably be done using namespaces? Assuming you're talking about only mboxes here, not maildirs.
Actually, in my example, / and /INBOX are mboxes ($HOME/mbox and /var/spool/<username> respectively), while everything in /folder are maildirs. The two wishes I've been trying to demonstrate in this example are: (1) dotless maildirs
Easy.
and subfolders,
Not that easy, but copy&pasting the code from mbox code to maildir code shouldn't be too difficult if you want it now instead of sometimes after v1.0.
and (2) mapping the IMAP root folder (I understood there is something like that, that is - IMAP mail folders are a rooted hierarchy) to some specific mbox/maildir.
There isn't such a thing as IMAP root folder.. INBOX is the closest thing to that.
participants (2)
-
Timo Sirainen
-
Tom Alsberg