similar to: imapc - different settings for different namespaces

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 > } >

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

----- Forwarded message from SerNet Support Lutz Pre?ler <support at SerNet.DE> ----- From: SerNet Support Lutz Pre?ler <support at SerNet.DE> Subject: 2.1: imapc LIST problem / usage question To: dovecot at 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

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 =

I think I have a working dovecot installation, and the time has come to migrate my users. There are only 4 of us, so it can be done manually per user. I looked at this page in the wiki http://wiki2.dovecot.org/Migration/Dsync but I am totally confused. 1st off, it uses doveadm, but with commands parameters that dont match my doveadm's man page. In fact they look more like dsync

Folks, I did read the documentation but I am at a loss still. I do have the following: Pass *createFooPass (char *foo1) { return new FooPass (foo1); } static RegisterPass<FooPass> X("foo-pass", "foo", false, true); Where exactly do I supply the non-default crore in this example ? Thanks /Dirk

http://dovecot.org/releases/2.2/dovecot-2.2.3.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.3.tar.gz.sig This is a pretty important upgrade for v2.2 users, because of the IMAP ENVELOPE reply fix. * LDA/LMTP: If new mail delivery first fails with "temporary failure", tempfail the whole delivery instead of falling back to delivering the mail to INBOX. (Requires new Pigeonhole

http://dovecot.org/releases/2.2/dovecot-2.2.3.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.3.tar.gz.sig This is a pretty important upgrade for v2.2 users, because of the IMAP ENVELOPE reply fix. * LDA/LMTP: If new mail delivery first fails with "temporary failure", tempfail the whole delivery instead of falling back to delivering the mail to INBOX. (Requires new Pigeonhole

Doing an imapc migration with the pop3 migration plugin, using doveadm backup -R. I occasionally get the following output: dsync(user at domain.tld): Error: imapc(mail01.domain.tld:143): Server disconnected unexpectedly dsync(user at domain.tld): Error: imapc(mail01.domain.tld:143): Server disconnected unexpectedly dsync(user at domain.tld): Error: imapc(mail01.domain.tld:143): Server

On Sep 30, 2013, at 10:11 PM, Dirk Schroetter <dschroetter at googlemail.com> wrote: > Folks, > > I did read the documentation but I am at a loss still. > > I do have the following: > > Pass *createFooPass (char *foo1) { > return new FooPass (foo1); > } > > static RegisterPass<FooPass> X("foo-pass", "foo", false, true); >

Does anyone know what the guidelines are supposed to be for properly initializing a pass? Looking around, we seem to have three styles of pass registration in use. INITIALIZE_PASS(...) INITIALIZE_PASS_BEGIN(...) INITIALIZE_PASS_DEPENDENCY(...) ... INITIALIZE_PASS_END(...) static RegisterPass<FooPass> X(...); (This is the one encouraged in the docs, but seemingly the least widely used

Hi, My end goal is to set up shared mailboxes on a cluster as per: https://wiki.dovecot.org/SharedMailboxes/ClusterSetup I was having very little luck with it, so I had been trying to break down into pieces and get individual components working. So I have things setup on a single server, with a working dovecot instance. I have no director or any thing else running yet, and I am just trying

Hi, I couldn't find any decent documentation about the IMAPC feature. Could someone please explain the purpose of this feature? In particular, what are the differences between IMAPC and reverse proxying? Thanks.

Hello (Timo), yes, I know... maybe it's a bit far fetched, but I do have a use case. Would it be (reasonably easily) possible to implement IMAP ACL support for "imported" imapc namespaces/mailboxes? There is no local directory (like with the virtual plugin) yet... Greetings, Lutz -- Lutz Pre?ler <Lutz.Pressler at SerNet.DE> http://www.SerNet.DE/ SerNet Service

On 09/08/2017 01:53 PM, Aki Tuomi wrote: > > On 08.09.2017 14:50, Nagy, Attila wrote: >> Hi, >> >> I've a broken IMAP server, which doesn't support pipelining and fails >> on dovecot's attempt to do this ([C] is dovecot's imapc, [S] is the >> IMAP server): >> >> [C] 24 LOGIN "user" "pass" >> [S] 23 OK

Hi, I've a broken IMAP server, which doesn't support pipelining and fails on dovecot's attempt to do this ([C] is dovecot's imapc, [S] is the IMAP server): [C] 24 LOGIN "user" "pass" [S] 23 OK [C] 25 SELECT "INBOX" [C] 23 UID FETCH 2 (INTERNALDATE) [S] 25 OK [S] 23 BAD No mailbox selected Sadly, fixing the server would be a hard task, turning off

On 09/11/2017 10:42 AM, Sami Ketola wrote: >> On 11 Sep 2017, at 11.24, Nagy, Attila <bra at fsn.hu> wrote: >> I use dovecot with a broken IMAP server (which doesn't properly implement command pipelining amongst others) as an imapc backend. >> Dovecot issues the above command sequence (SELECT and UID FETCH pipelined), which doesn't work with this server. >>

On 09/11/2017 09:17 AM, Aki Tuomi wrote: > > On 08.09.2017 15:29, Nagy, Attila wrote: >> On 09/08/2017 01:53 PM, Aki Tuomi wrote: >>> On 08.09.2017 14:50, Nagy, Attila wrote: >>>> Hi, >>>> >>>> I've a broken IMAP server, which doesn't support pipelining and fails >>>> on dovecot's attempt to do this ([C] is

I received this error at the end of a migration from imapc to mdbox. Is it because I wanted doveadm 'sync' instead of 'backup'? I didn't get time to do any testing, but since you're pushing for the release, here it is: kerio2:~ adminuser$ /opt/dovecot/bin/doveadm -o imapc_user=jsample -o imapc_password=****** -o imapc_host=*.*.*.* sync -R -u jsample_dc at mydomain.com

Hi, This is a capture from an imapc client session (which is triggered by a message, received via LMTP): * OK [CAPABILITY IMAP4rev1 NAMESPACE] Ready 2 LOGIN "uid" "pass" 2 OK LOGIN succeeded 1 LIST "" "" * LIST (\Noselect) "/" "" 1 OK LIST completed 3 APPEND "INBOX" {568} + Ready for 568 octets of data [...] 3 OK APPEND