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. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: <http://dovecot.org/pipermail/dovecot/attachments/20050807/7e6ffe98/attachment.bin>