search for: necoro

Hi, after migrating to 2.2 (currently using 2.2.5), I see strange error messages when using imapc + public namespace + acl My setup: I create a public shared mailbox with imapc as location. Then I restrict this mailbox to one user only using ACLs. This works for this one special user, but for all others an error gets logged and they can't access their mailbox anymore: Sep 24 18:09:46

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

Hi, I have managed to get an imapc connection to another server and bind its contents to only one account (via global ACL). The namespace itself is created as public, though it does not seem to make a difference for this use case (i.e., it does not matter, whether its type is 'public', 'shared', or 'private'). namespace { hidden = no list = children location =

Hi, I've got two questions regarding imapc and namespaces: 1) Is there a way of stating, that I only want part of the hierarchy on the end of an imapc connection to be available here? My "problem": On the other end the layout is: INBOX.Shared.{some,nice,folders} If I mirror this into my dovecot hierarchy with prefix "Gemeinsam" I get the following folder structure:

Hi *, I am adding a generic way for vacation-replies in my sieve setup. There I set the handle and the reason using variables (see end of mail). My simple question now is: Though variable expansion is not done for subject and reason, is it done for the handle? Because else there seems no way in configuring the vacation action via variables. I tried to read the code for this extension, but ...