search for: imapc_

...Is there an error, or am I totally misunderstanding 2nd - if I assume its a dsync set of parameters, the imapc: at the end is a specification of location2. However, again my man page doesn't give any explanation of this. I am wondering, is this an example of an proxy 3rd - where do the imapc_* parameters go in the configuration I can't find any reference to them in the wiki

Originally I was planning on allowing all kinds of mail settings inside namespace {}, including imapc_* settings. But that's a bit difficult to implement (although I think it will happen some day). So for now I was thinking: imapc foo { host = imap.foo.com master_user = foomaster password = foopass } imapc bar { host = imap.bar.com ... } namespace { prefix = foo/ location = imap...

...ldren location = imapc: prefix = Gemeinsam. separator = . subscriptions = no type = public } One problem remains: Though there is only one account that is allowed to use this imapc-connection, each imap-process opens a connection to the imapc'd server. Is this caused directly by the imapc_*-definitions in the config? Or is there a way of restricting this to only the account which actually uses it. Used dovecot version: 2.1.8 Thanks, Ren?

...uild 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 at 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....

On 05/31/2013 04:21 PM, Timo Sirainen wrote: > Originally I was planning on allowing all kinds of mail settings inside namespace {}, including imapc_* settings. But that's a bit difficult to implement (although I think it will happen some day). So for now I was thinking: > > imapc foo { > host = imap.foo.com > master_user = foomaster > password = foopass > } > > imapc bar { > host = imap.bar.com >...

...ad OK. POP3 UIDLs are also ok (tested for one user). (1) My question is how can I make the source remain same (unread status etc.) so that I do migrate the various domains in a transparent manner and then switch servers ?. I have multiple virtual domains. (2) One more question do I have to do both imapc_ & also pop3c_ migration since I need the POP UIDLs to work properly for my outlook POP3 users after migration ?. Thanks DP --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

...ad OK. POP3 UIDLs are also ok (tested for one user). (1) My question is how can I make the source remain same (unread status etc.) so that I do migrate the various domains in a transparent manner and then switch servers ?. I have multiple virtual domains. (2) One more question do I have to do both imapc_ & also pop3c_ migration since I need the POP UIDLs to work properly for my outlook POP3 users after migration ?. I want to know the possibilities. Thanks DP --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

Hi *, I can't find any decent information about the capabilities of imapc in the planned future dovecot releases. As I think about using imapc, I'll just give the two use-cases I see for me. Will this be possible with imapc? 1) One (or more) folders in a mailbox which are proxied? 2) Proxy a whole mailbox _and use the folders in it as shared folders_. That means account X on Server 1

Hello, I'm using various password databases (one of them is a ldap database, which is the used for users connecting with email clients, and the other with pam, using a pam module integrated with our SSO that is used from our webmail). I would like to disable password caching in my pam database (because 'passwords' provided by our SSO are single use tokens, so caching them has no

...ously and prefetched as much as possible. For per-mail annotation lookups mail_alloc() needs to include a list of annotations that are wanted. Configuration ------------- Copy all mail settings to namespaces, so it'll be possible to use per-namespace mailbox settings. Especially important for imapc_* settings, but can be useful for others as well. Those settings that aren't explicitly defined in the namespace will use the global defaults. (Should doveconf -a show all of these values, or simply the explicitly set values?) Get rid of *.conf.ext files. Make everything part of dovecot.conf, s...