subscription namespace

[Daniel Miller via dovecot]

The current documentation makes mention of a "special" subscription 
namespace. The example given:


namespace subscriptions {
  subscriptions = yes
  prefix = ""
  list = no
  hidden = yes
}

namespace inbox {
  inbox = yes
  location =
  subscriptions = no
[...]

results in a startup error as both namespaces have the same prefix. Was 
the intent for the "inbox" namespace to have an explicit "INBOX/" prefix?


If this is configured for an existing server that previously had no such 
"INBOX/" prefix namespace - will clients need to be reconfigured?


--
Daniel

[Dovecot] NO Unknown subscription namespace.

[mailing lists]

Hello,

what this message means?

NO Unknown subscription namespace.

the shared namespace is visible and I can fetch messages from it, but 
subscription fails with the above message.

(user002 is sharing the folder named docs-users002 with user user001)


# telnet localhost 143
Trying ::1...
Connected to localhost.
Escape character is '^]'.
* OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE 
AUTH=PLAIN] Dovecot ready.
. login user001 secret
. OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT 
SORT=DISPLAY THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT CHILDREN 
NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT 
SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS ACL RIGHTS=texk] Logged in
. list shared. *
* LIST (\Noselect \HasChildren) . shared.user002
. OK List completed.
. list shared.user002. *
* LIST (\HasNoChildren) . shared.user002.docs-user002
. OK List completed.
. list shared.user002.docs-user002. *
. OK List completed.
. select shared.user002.docs-user002
* FLAGS (\Answered \Flagged \Deleted \Seen \Draft)
* OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft)] Flags 
permitted.
* 2 EXISTS
* 0 RECENT
* OK [UIDVALIDITY 1315765265] UIDs valid
* OK [UIDNEXT 3] Predicted next UID
* OK [HIGHESTMODSEQ 3] Highest
. OK [READ-WRITE] Select completed.
. fetch 1 all
* 1 FETCH (FLAGS (\Seen) INTERNALDATE 24-Nov-2009 11:58:34 +0100 RFC822.SIZE 
3734 ENVELOPE (Tue, 24 Nov 2009 07:58:34 -0400 (AST) Thank you for 
registering for the Red Hat Virtual Experience 
((supp...@virtualevents365.com NIL support virtualevents365.com)) 
((supp...@virtualevents365.com NIL support virtualevents365.com)) 
((supp...@virtualevents365.com NIL support virtualevents365.com)) 
((damocl...@hotmail.com NIL damocles- hotmail.com)) NIL NIL NIL 
6955854.2731259063914762.javamail.r...@app130.vs.int.cgsinc.ca))
. OK Fetch completed.
. subscribe shared.user002.docs-user002
. NO Unknown subscription namespace.
. logout
* BYE Logging out
. OK Logout completed.
Connection closed by foreign host.

 //

namespace {
  inbox = yes
  location = 
  prefix = INBOX.
  separator = .
  subscriptions = yes
}
namespace {
  list = yes
  location = maildir:/var/virtual-maildir/%%n
  prefix = shared.%%n.
  separator = .
  subscriptions = no
  type = shared
}

Re: [Dovecot] NO Unknown subscription namespace.

[Timo Sirainen]

On Mon, 2011-09-12 at 09:14 +0100, mailing lists wrote:
 Hello,
 
 what this message means?
 
 NO Unknown subscription namespace.

It means that the namespace itself has subscriptions=no, and there are
no parent namespaces with subscriptions=yes.

 namespace {
   inbox = yes
   location = 
   prefix = INBOX.
   separator = .
   subscriptions = yes
 }
 namespace {
   list = yes
   location = maildir:/var/virtual-maildir/%%n
   prefix = shared.%%n.
   separator = .
   subscriptions = no
   type = shared
 }

I guess you'd want INBOX. namespace to handle the subscriptions here,
but it doesn't work like that because in some configuration it could be
ambiguous which namespace to use.. You'll need to create a prefix=
namespace to handle the subscriptions. For example:

namespace {
  prefix =
  list = no
  hidden = yes
}