[Dovecot] dot named folders
When a user makes a folder called 'x.y' it actually creates a folder called 'x' with a folder called 'y' inside, rather than a folder called 'x.y'. I'm guessing this has to do with an internal folder separator namespace configuration, but I'm a bit confused by how this works.
I'm using 2.0.15 with mdbox and this is what I have configured for my namespaces:
namespace { separator = . prefix = inbox = yes }
namespace { separator = . prefix = INBOX. inbox = no hidden = yes list = no }
I migrated from courier maildirs, so perhaps I no longer need some of these now that the conversion is finished?
thanks for any suggestions, I've got my head mixed up on this issue, micah
--
On 03/07/2012 12:43 PM, Micah Anderson wrote:
When a user makes a folder called 'x.y' it actually creates a folder called 'x' with a folder called 'y' inside, rather than a folder called 'x.y'. I'm guessing this has to do with an internal folder separator namespace configuration, but I'm a bit confused by how this works.
Correct. Similar to how in Linux, I could create a folder mkdir test1/test2 It will create test2 inside of test1.
The difference being that IMAP doesn't necessarily need the parent mailbox to exist, where Linux would throw an error if test1/ didn't exist first.
So basically, as far as I know, you can't have a folder with a "." in the name with the namespaces you have set up.
Willie Gillespie <wgillespie+dovecot@es2eng.com> writes:
On 03/07/2012 12:43 PM, Micah Anderson wrote:
When a user makes a folder called 'x.y' it actually creates a folder called 'x' with a folder called 'y' inside, rather than a folder called 'x.y'. I'm guessing this has to do with an internal folder separator namespace configuration, but I'm a bit confused by how this works.
Correct. Similar to how in Linux, I could create a folder mkdir test1/test2 It will create test2 inside of test1.
The difference being that IMAP doesn't necessarily need the parent mailbox to exist, where Linux would throw an error if test1/ didn't exist first.
So basically, as far as I know, you can't have a folder with a "." in the name with the namespaces you have set up.
That makes sense, however I'm not sure that I need these namespaces any longer if I no longer am using the maildir format (mdbox).
In either case, it seems like the internal folder separator should not be exposed to the user like this. What is happening now is the user gets something other than they expect (a folder within a folder, instead of a folder with a dot in the name) because of some unknown internal configuration.
If moving to mdbox is not enough to remove these namespace configurations that cause this, then it would be good if the user was unable to create such a folder, because it was prohibited, rather than creating something other than they expect.
micah
Am 08.03.2012 17:27, schrieb Micah Anderson:
Willie Gillespie <wgillespie+dovecot@es2eng.com> writes:
On 03/07/2012 12:43 PM, Micah Anderson wrote:
When a user makes a folder called 'x.y' it actually creates a folder called 'x' with a folder called 'y' inside, rather than a folder called 'x.y'. I'm guessing this has to do with an internal folder separator namespace configuration, but I'm a bit confused by how this works.
Correct. Similar to how in Linux, I could create a folder mkdir test1/test2 It will create test2 inside of test1.
The difference being that IMAP doesn't necessarily need the parent mailbox to exist, where Linux would throw an error if test1/ didn't exist first.
So basically, as far as I know, you can't have a folder with a "." in the name with the namespaces you have set up.
That makes sense, however I'm not sure that I need these namespaces any longer if I no longer am using the maildir format (mdbox).
In either case, it seems like the internal folder separator should not be exposed to the user like this. What is happening now is the user gets something other than they expect (a folder within a folder, instead of a folder with a dot in the name) because of some unknown internal configuration.
If moving to mdbox is not enough to remove these namespace configurations that cause this, then it would be good if the user was unable to create such a folder, because it was prohibited, rather than creating something other than they expect.
micah
http://wiki.dovecot.org/Plugins/Listescape may help
-- Best Regards
MfG Robert Schetterer
Germany/Munich/Bavaria
Robert Schetterer <robert@schetterer.org> writes:
Am 08.03.2012 17:27, schrieb Micah Anderson:
Willie Gillespie <wgillespie+dovecot@es2eng.com> writes:
On 03/07/2012 12:43 PM, Micah Anderson wrote:
When a user makes a folder called 'x.y' it actually creates a folder called 'x' with a folder called 'y' inside, rather than a folder called 'x.y'. I'm guessing this has to do with an internal folder separator namespace configuration, but I'm a bit confused by how this works.
Correct. Similar to how in Linux, I could create a folder mkdir test1/test2 It will create test2 inside of test1.
The difference being that IMAP doesn't necessarily need the parent mailbox to exist, where Linux would throw an error if test1/ didn't exist first.
So basically, as far as I know, you can't have a folder with a "." in the name with the namespaces you have set up.
That makes sense, however I'm not sure that I need these namespaces any longer if I no longer am using the maildir format (mdbox).
In either case, it seems like the internal folder separator should not be exposed to the user like this. What is happening now is the user gets something other than they expect (a folder within a folder, instead of a folder with a dot in the name) because of some unknown internal configuration.
If moving to mdbox is not enough to remove these namespace configurations that cause this, then it would be good if the user was unable to create such a folder, because it was prohibited, rather than creating something other than they expect.
micah
Interesting, thanks for the pointer, although I think I prefer if users are just prohibited from making a 'folder.withadot' and told that it is prohibited right away, rather than giving them a way to do it.
micah
--
On 7.3.2012, at 21.43, Micah Anderson wrote:
When a user makes a folder called 'x.y' it actually creates a folder called 'x' with a folder called 'y' inside, rather than a folder called 'x.y'. I'm guessing this has to do with an internal folder separator namespace configuration, but I'm a bit confused by how this works.
I'm using 2.0.15 with mdbox and this is what I have configured for my namespaces:
namespace { separator = . prefix = inbox = yes }
Keep this.
namespace { separator = . prefix = INBOX. inbox = no hidden = yes list = no }
I migrated from courier maildirs, so perhaps I no longer need some of these now that the conversion is finished?
It depends on if you have any users whose clients are using INBOX. namespace. If there are, and you remove it, the users won't see anything except INBOX anymore.
participants (4)
-
Micah Anderson
-
Robert Schetterer
-
Timo Sirainen
-
Willie Gillespie