similar to: imapc and imap_acl

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

On Thu, 15 Sep 2011, Timo Sirainen wrote: > On Wed, 2011-09-14 at 12:10 +0200, Lutz Pre?ler wrote: > > imap(2717, testuser): Panic: file mailbox-list-subscriptions.c: line > > 66 (mailbox_list_subscription_fill_one): assertion failed: (ns!= NULL > > && (ns->flags & NAMESPACE_FLAG_AUTOCREATED) != 0) > > > Fixed:

Hello, with imapc settings coming from userdb (individual configuration necessary) there exists a security problem if access to auth-userdb socket is given to normal (shell) users: testuser at host:~$ doveadm user user1 userdb: lpmail uid : 1000 gid : 1111 home : /home/user1 namespace : gmail namespace/gmail/list: yes namespace/gmail/subscriptions: no

Hi ! I have an old Courier IMAP and in front of it, I have put a proxy cache with Dovecot/imapc. I use Debian Wheezy (stable) which package Dovecot in version 2.1.7. I have tested the upgrade to Debian Jessie (testing) which package Dovecot in version 2.2.9 but an assertion is thrown : dovecot: imap(xxx): Panic: file imapc-list.c: line 499 (imapc_list_delete_unused_indexes): assertion failed:

> On 31 Mar 2020, at 23.18, Ben Mulvihill <ben.mulvihill at gmail.com> wrote: > > Hello again, > > I am still stuck I'm afraid. > > I now have doveadm backup working perfectly from > a small gmail mailbox (a few hundred messages), but > when I try the same configuration (apart from usernames > and passwords obviously) with a large gmail mailbox >

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 =

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

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

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

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

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

On 09/11/2017 11:14 AM, Aki Tuomi wrote: > > On 11.09.2017 11:59, Nagy, Attila wrote: >> 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.

I am trying to backup a gmail account (not the one I am writing from) to dovecot, using doveadm-backup and imapc, but am having ssl connection problems. ted at expectation:~# doveadm backup -D -R -u ted imapc: dsync(ted): Info: imapc(imap.gmail.com:993): Connected to 74.125.71.108:993 (local 10.7.1.179:53852) dsync(ted): Warning: imapc(imap.gmail.com:993): Server disconnected unexpectedly:

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

I just committed a very early initial implementation of "imapc" storage backend to v2.1 hg: http://hg.dovecot.org/dovecot-2.1 You can't really do anything except open INBOX and read mails from it, so it's currently only intended for initial testing. It sucks in many ways right now, but I'll be improving it. The idea is that you could set for example: mail_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:

We're using doveadm/dsync/imapc to migrate accounts from Courier to Dovecot 2.2.20. On the source-server some user have folder names including a "%" in their name. Looks like doveadm isn't able to handle that folder names. I always stops with: dsync(testtest): Error: Failed to access mailbox INBOX.Test%TEST: Mailbox does not exist, or must be subscribed to. Peer --