[Dovecot] 2.1: imapc LIST problem / usage question
----- Forwarded message from SerNet Support Lutz Preßler <support@SerNet.DE> -----
From: SerNet Support Lutz Preßler <support@SerNet.DE> Subject: 2.1: imapc LIST problem / usage question To: dovecot@dovecot.org Date: Fri, 9 Sep 2011 12:00:46 +0200 Organization: SerNet Service Network GmbH
Hello,
2.1.alpha1 (latest Debian auto build on amd64)
As a test, namespace for gmail integration set up by userdb with userdb_namespace=gmail userdb_namespace/gmail/list=yes userdb_namespace/gmail/subscriptions=no userdb_namespace/gmail/separator=. userdb_namespace/gmail/prefix=INBOX.gmail. userdb_namespace/gmail/location=imapc: userdb_imapc_host=imap.gmail.com userdb_imapc_user=ixxxxx@gmail.com userdb_imapc_password=xxxxx userdb_imapc_ssl=imaps userdb_imapc_ssl_ca_dir=/etc/ssl/certs userdb_imapc_port=993
(but having the namespace set up in config file makes no difference).
This works in principle. I can e.g.
0 select "INBOX.gmail.[Gmail].Alle Nachrichten"
- FLAGS (\Answered \Flagged \Deleted \Seen \Draft)
- OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted.
- 31 EXISTS
- 0 RECENT
- OK [UNSEEN 1] First unseen.
- OK [UIDVALIDITY 1] UIDs valid
- OK [UIDNEXT 19689] Predicted next UID
- OK [NOMODSEQ] No permanent modsequences 0 OK [READ-WRITE] Select completed.
and even use the gmail mailboxes within dovecot-virtual files!
But: LIST seems broken:
0 list "" "*"
- LIST (\HasChildren) "." "INBOX"
- LIST (\HasNoChildren) "." "INBOX.privat"
- LIST (\HasChildren) "." "INBOX.test"
- LIST (\HasNoChildren) "." "INBOX.test.test2"
- LIST (\HasNoChildren) "." "INBOX.Trash"
- LIST (\HasNoChildren) "." "INBOX.in2009" [...]
- LIST (\Noselect \HasChildren) "." "INBOX.gmail"
- LIST (\HasNoChildren) "." "Arbeit"
- LIST (\HasNoChildren) "." "Belege"
- LIST (\HasNoChildren) "." "Privat"
- LIST (\HasNoChildren) "." "Reisen"
- LIST (\Noselect \HasNoChildren) "." "[Gmail]"
- LIST (\HasNoChildren) "." "[Gmail]/Alle Nachrichten"
- LIST (\HasNoChildren) "." "[Gmail]/Entw&-APw-rfe"
- LIST (\HasNoChildren) "." "[Gmail]/Gesendet"
- LIST (\HasNoChildren) "." "[Gmail]/Markiert"
- LIST (\HasNoChildren) "." "[Gmail]/Papierkorb"
- LIST (\HasNoChildren) "." "[Gmail]/Spam"
- LIST (\HasNoChildren) "." "[Gmail]/Wichtig"
- LIST (\HasChildren) "." "INBOX.virtual"
- LIST (\HasNoChildren) "." "INBOX.virtual.week"
- LIST (\HasNoChildren) "." "INBOX.virtual.sent"
- LIST (\HasNoChildren) "." "INBOX.virtual.allin" 0 OK List completed.
For the Gmail mailboxe the INBOX.gmail prefix is missing and / is used as separator.
Second question: Is there a way to include multiple imapc instances/ namespaces with e.g. different destinations servers? I don't see how because imapc_* parameters seem to be global (now), but it would be a very useful feature.
Greetings, Lutz
On Fri, 2011-09-09 at 12:01 +0200, Lutz Preßler wrote:
As a test, namespace for gmail integration set up by userdb with userdb_namespace=gmail userdb_namespace/gmail/list=yes userdb_namespace/gmail/subscriptions=no userdb_namespace/gmail/separator=. userdb_namespace/gmail/prefix=INBOX.gmail. userdb_namespace/gmail/location=imapc: userdb_imapc_host=imap.gmail.com userdb_imapc_user=ixxxxx@gmail.com userdb_imapc_password=xxxxx userdb_imapc_ssl=imaps userdb_imapc_ssl_ca_dir=/etc/ssl/certs userdb_imapc_port=993
For the Gmail mailboxe the INBOX.gmail prefix is missing and / is used as separator.
Fixed in hg.
Second question: Is there a way to include multiple imapc instances/ namespaces with e.g. different destinations servers? I don't see how because imapc_* parameters seem to be global (now), but it would be a very useful feature.
I don't really understand. You're already returning per-user imapc namespace from userdb. What's missing?
On Fr, 09 Sep 2011, Timo Sirainen wrote:
On Fri, 2011-09-09 at 12:01 +0200, Lutz Preßler wrote: [...]
For the Gmail mailboxe the INBOX.gmail prefix is missing and / is used as separator.
Fixed in hg. Thanks.
Second question: Is there a way to include multiple imapc instances/ namespaces with e.g. different destinations servers? I don't see how because imapc_* parameters seem to be global (now), but it would be a very useful feature.
I don't really understand. You're already returning per-user imapc namespace from userdb. What's missing? One local dovecot user, multiple remote IMAP servers included in different namespaces.
Lutz
On Fri, 2011-09-09 at 12:21 +0200, Lutz Preßler wrote:
Second question: Is there a way to include multiple imapc instances/ namespaces with e.g. different destinations servers? I don't see how because imapc_* parameters seem to be global (now), but it would be a very useful feature.
I don't really understand. You're already returning per-user imapc namespace from userdb. What's missing? One local dovecot user, multiple remote IMAP servers included in different namespaces.
I think you should be able to return e.g. "namespace=ns1 ns2" and then return namespaces for namespace/ns1/* and namespace/ns2/*.
On Mo, 12 Sep 2011, Timo Sirainen wrote:
On Fri, 2011-09-09 at 12:21 +0200, Lutz Preßler wrote:
Second question: Is there a way to include multiple imapc instances/ namespaces with e.g. different destinations servers? I don't see how because imapc_* parameters seem to be global (now), but it would be a very useful feature.
I don't really understand. You're already returning per-user imapc namespace from userdb. What's missing? One local dovecot user, multiple remote IMAP servers included in different namespaces.
I think you should be able to return e.g. "namespace=ns1 ns2" and then return namespaces for namespace/ns1/* and namespace/ns2/*. Now _I_ don't really understand ;-). This is necessary, yes, but how do I set different remote parameters (imapc_host, imapc_user, ...) for each one?
Lutz
On Mon, 2011-09-12 at 13:20 +0200, Lutz Preßler wrote:
I think you should be able to return e.g. "namespace=ns1 ns2" and then return namespaces for namespace/ns1/* and namespace/ns2/*. Now _I_ don't really understand ;-). This is necessary, yes, but how do I set different remote parameters (imapc_host, imapc_user, ...) for each one?
Oh, yeah, didn't think about that :) I was considering making those settings per-namespace though.. Then you could change namespace/ns1/imapc_* settings. I guess most mail-related settings could be made per-namespace. I'll see if I can manage to do it easily. :)
participants (2)
-
Lutz Preßler
-
Timo Sirainen