I am trying to configure dovecot-1.2.11 to have the same IMAP namespacing as
courier-imap as per http://wiki.dovecot.org/Migration/Courier, but failing
badly.
I have a test maildir with INBOX and folder 'junk'. Without fiddling
with
namespaces, this works fine: there are 91 msgs in INBOX and 2 in junk.
a namespace
* NAMESPACE (("" ".")) NIL NIL
a OK Namespace completed.
a examine INBOX
...
* 91 EXISTS
...
a OK [READ-ONLY] Select completed.
a examine junk
...
* 2 EXISTS
...
a OK [READ-ONLY] Select completed.
Now I make the following addition to dovecot.conf:
namespace private {
separator = .
prefix = INBOX.
inbox = yes
hidden = no
}
After this the inbox appears to be empty, and I cannot select the junk
folder at all:
a namespace
* NAMESPACE (("INBOX." ".")) NIL NIL
a OK Namespace completed.
a examine INBOX
* FLAGS (\Answered \Flagged \Deleted \Seen \Draft)
* OK [PERMANENTFLAGS ()] Read-only mailbox.
* 0 EXISTS
* 0 RECENT
* OK [UIDVALIDITY 1269605071] UIDs valid
* OK [UIDNEXT 1] Predicted next UID
* OK [HIGHESTMODSEQ 1] Highest
a OK [READ-ONLY] Select completed.
a examine INBOX.junk
* OK [CLOSED] Previous mailbox closed.
a NO Mailbox doesn't exist: junk
Furthermore I can select "INBOX.INBOX" (although that's empty as
well)
a examine INBOX.INBOX
* FLAGS (\Answered \Flagged \Deleted \Seen \Draft)
* OK [PERMANENTFLAGS ()] Read-only mailbox.
* 0 EXISTS
* 0 RECENT
* OK [UIDVALIDITY 1269605071] UIDs valid
* OK [UIDNEXT 1] Predicted next UID
* OK [HIGHESTMODSEQ 1] Highest
a OK [READ-ONLY] Select completed.
a examine INBOX.INBOX.INBOX
* OK [CLOSED] Previous mailbox closed.
a NO Mailbox doesn't exist: INBOX.INBOX
a examine junk
a NO Unknown namespace.
Have I misunderstood what I'm supposed to be doing here?
The other relevant setting is:
mail_location: maildir:%h
but I've not changed this; as I say, this works just fine without meddling
with namespaces.
Many thanks,
Brian.
On Fri, 2010-03-26 at 12:36 +0000, Brian Candler wrote:> Now I make the following addition to dovecot.conf: > > namespace private { > separator = . > prefix = INBOX. > inbox = yes > hidden = no > } > > After this the inbox appears to be empty, and I cannot select the junk > folder at all:Something's seriously wrong. Just changing namespace prefix shouldn't do anything like that. (And since I haven't heard of horror stories of v1.2.11 breaking, I don't think I just broke it either.) What does this show: a LIST "" * Also, make sure that dovecot -n shows only that one namespace you defined with the exact settings you intended. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part URL: <http://dovecot.org/pipermail/dovecot/attachments/20100326/93dd5b81/attachment-0002.bin>
On Fri, Mar 26, 2010 at 02:45:40PM +0200, Timo Sirainen wrote:> > After this the inbox appears to be empty, and I cannot select the junk > > folder at all: > > Something's seriously wrong. Just changing namespace prefix shouldn't do > anything like that. (And since I haven't heard of horror stories of > v1.2.11 breaking, I don't think I just broke it either.) > > What does this show: > > a LIST "" *a list "" * * LIST (\HasChildren) "." "INBOX" a OK List completed.> Also, make sure that dovecot -n shows only that one namespace you > defined with the exact settings you intended.Yes, it was fine. However, I've now found the problem using ktrace. The homedir attribute in LDAP is /mail/0/6/37/30/brian%dev.example.com/ but when I do 'examine inbox' I see it has been munged: 30362 imap GIO fd 0 read 17 bytes "a examine INBOX\r " 30362 imap RET read 17/0x11 30362 imap CALL stat(0x186012a0,0xbfbfe4b0) 30362 imap NAMI "/mail/0/6/37/30/briandev.example.comev.example.com/tmp" Furthermore, I can make it work properly just by adding ... location = maildir:%h ... inside the 'namespace' setting, rather than relying on it defaulting to the mail_location setting (which is the same as that) So it looks like "%dev..." was having "%d" expanded. As I have a config workaround it's not a big deal, but it certainly was confusing; maybe this is one level of attribute expansion which you didn't intend taking place. Regards, Brian.