[Dovecot] shared/public mailbox doesn't exist
I have 3 servers running dovecot 1.0.10. 2 of them are configured with a shared/public namespace, but I'm having trouble getting it to work on the third, even with 2 working examples to go by. There's something I'm missing, and I'm hoping that someone here can see/tell what it is.
I've created the maildir for sharing: # cd /home/vpopmail/domains/mydomain.com # maildirmake shared # chown -R vpopmail:vchkpw shared
Then added the configuration to dovecot.conf: # shared namespace namespace shared { separator = . prefix = shared. location = maildir:/home/vpopmail/domains/mydomain.com/shared }
Restarted dovecot: # service dovecot restart
When I try to subscribe to the shared namespace though with Outlook, I get: "Failed to subscribe the folder. Server responded: 'Mailbox doesn't exist: shared'." When I try to subscribe with Squirrelmail I get: "ERROR: Could not complete request. Query: SUBSCRIBE "shared" Reason Given: [TRYCREATE] Mailbox doesn't exist: shared"
I've tried various combinations of permissions to no avail.
Suggestions welcome. I'm at my wits end.
-- -Eric 'shubes'
Eric Shubert wrote:
I have 3 servers running dovecot 1.0.10. 2 of them are configured with a shared/public namespace, but I'm having trouble getting it to work on the third, even with 2 working examples to go by. There's something I'm missing, and I'm hoping that someone here can see/tell what it is.
I've created the maildir for sharing: # cd /home/vpopmail/domains/mydomain.com # maildirmake shared # chown -R vpopmail:vchkpw shared
Then added the configuration to dovecot.conf: # shared namespace namespace shared { separator = . prefix = shared. location = maildir:/home/vpopmail/domains/mydomain.com/shared }
Restarted dovecot: # service dovecot restart
When I try to subscribe to the shared namespace though with Outlook, I get: "Failed to subscribe the folder. Server responded: 'Mailbox doesn't exist: shared'." When I try to subscribe with Squirrelmail I get: "ERROR: Could not complete request. Query: SUBSCRIBE "shared" Reason Given: [TRYCREATE] Mailbox doesn't exist: shared"
I've tried various combinations of permissions to no avail.
Suggestions welcome. I'm at my wits end.
So I created a few subfolders. # cd /home/vpopmail/domains/mydomain.com/shared # maildirmake .sub1 # maildirmake .sub2 # chown vpopmail:vchkpw sub*
Voila, sort of. The main folder named 'shared' cannot be subscribed to, however sub1 and sub2 can be subscribed to successfully.
Can someone explain why that is? Thanks.
-Eric 'shubes'
On Sep 22, 2009, at 4:49 AM, Eric Shubert wrote:
namespace shared { separator = . prefix = shared. location = maildir:/home/vpopmail/domains/mydomain.com/shared }
So I created a few subfolders. # cd /home/vpopmail/domains/mydomain.com/shared # maildirmake .sub1 # maildirmake .sub2 # chown vpopmail:vchkpw sub*
Voila, sort of. The main folder named 'shared' cannot be subscribed
to, however sub1 and sub2 can be subscribed to successfully.
That's because "shared" is a namespace prefix and not a folder. There
shouldn't be any reason to subscribe to it. But, anyway, Dovecot v1.2
allows you to subscribe to it anyway.
Timo Sirainen wrote:
On Sep 22, 2009, at 4:49 AM, Eric Shubert wrote:
namespace shared { separator = . prefix = shared. location = maildir:/home/vpopmail/domains/mydomain.com/shared }
So I created a few subfolders. # cd /home/vpopmail/domains/mydomain.com/shared # maildirmake .sub1 # maildirmake .sub2 # chown vpopmail:vchkpw sub*
Voila, sort of. The main folder named 'shared' cannot be subscribed to, however sub1 and sub2 can be subscribed to successfully.
That's because "shared" is a namespace prefix and not a folder. There shouldn't be any reason to subscribe to it. But, anyway, Dovecot v1.2 allows you to subscribe to it anyway.
Thanks Timo.
Looks like it'll be time for me to upgrade soon so I can have fully supported shared mailboxes. Is v1.2.5 considered stable/production grade?
-- -Eric 'shubes'
On Sep 22, 2009, at 5:55 PM, Eric Shubert wrote:
That's because "shared" is a namespace prefix and not a folder.
There shouldn't be any reason to subscribe to it. But, anyway,
Dovecot v1.2 allows you to subscribe to it anyway.Thanks Timo.
Looks like it'll be time for me to upgrade soon so I can have fully
supported shared mailboxes.
I've never understood why people so desperately want to try to
subscribe to the shared namespace prefix. I only added that feature
because so many people kept asking about it. Do you have a reason why
you want to do it?
Is v1.2.5 considered stable/production grade?
Sure.
Timo Sirainen wrote:
On Sep 22, 2009, at 5:55 PM, Eric Shubert wrote:
That's because "shared" is a namespace prefix and not a folder. There shouldn't be any reason to subscribe to it. But, anyway, Dovecot v1.2 allows you to subscribe to it anyway.
Thanks Timo.
Looks like it'll be time for me to upgrade soon so I can have fully supported shared mailboxes.
I've never understood why people so desperately want to try to subscribe to the shared namespace prefix. I only added that feature because so many people kept asking about it. Do you have a reason why you want to do it?
Not a good reason, but I think that's only because I planned to put subfolders in the namespace. I can think of 2 reasons why people might want to do this though.
First, if they only have one folder that they want to share in the namespace, why would/should they have to create a folder under the namespace? Why not simply treat the namespace as a folder and put the mail in there? It's simpler that way.
The second reason is because it appears to be possible to subscribe to the namespace in their client program, at least until they actually try to subscribe to it. TBird does a much better presentation than other IMAP clients in this regard, as it won't let you select the namespace for subscription (with Dovecot 1.0). Outlook and Squirrelmail, on the other hand, allow you to select the namespace and attempt to subscribe to it. This leads users to believe that they should be able to subscribe to the namespace, whether the server allows it or not. I think this is probably a more significant reason than the first one.
Is v1.2.5 considered stable/production grade?
Sure.
Great. I'll be upgrading when I get a chance. I haven't checked the wiki about upgrading yet. As long as I'm here though I'll shamefully ask, are there any gotchas upgrading from 1.0 to 1.2? A link to a relevant web page will more than suffice. Thanks.
-- -Eric 'shubes'
participants (2)
-
Eric Shubert
-
Timo Sirainen