similar to: migration from zimbra to dovecot

> On 31 Oct 2016, at 13.11, Tanstaafl <tanstaafl at libertytrek.org> wrote: > > On 10/30/2016 5:32 AM, Sami Ketola <sami.ketola at dovecot.fi> wrote: >> On 28 Oct 2016, at 16.54, Tanstaafl <tanstaafl at libertytrek.org> wrote: >>> Oh... I thought the --useuid option eliminated this problem? >>> >>>

> > >> On 30 Sep 2019, at 13.13, tovises via dovecot <dovecot at dovecot.org> >> wrote: >>> >> WOW! - amazing quickly, I'm really grateful. >> >> I was using: -u tovis imapc: nusi but still something wrong. >> Patstebin: https://pastebin.com/tH4wzJka >> The most relevant part (I think) is: >>

> > On 30.9.2019 13.40, tovises wrote: >>> >>>> On 30 Sep 2019, at 13.13, tovises via dovecot <dovecot at dovecot.org> >>>> wrote: >>>> WOW! - amazing quickly, I'm really grateful. >>>> >>>> I was using: -u tovis imapc: nusi but still something wrong. >>>> Patstebin: https://pastebin.com/tH4wzJka

Due to the incompatibilities with the dsync protocol version between 2.1 and 2.2, I am unable to use dsync to move users to a new machine where we have 2.2.5 setup. This wouldn't normally be a problem, as I could just rsync the user's mdbox and dovecot would happily do the right thing. However, on the new system I've placed the indexes into a faster storage medium, where on the older

Hello, I'm using 2.2.13 on Debian stable, and I perform regular dsync backups. Typically if there is an error, dsync can recover from it the next time it is run, but I've been encountering a new error that doesn't seem to self-heal: # /usr/bin/dsync -u gae backup ssh -i /root/.ssh/id_rsa backmaildir at internal.example /usr/bin/dsync -u micah dsync-remote(micah): Error:

> > On 30.9.2019 12.38, tovises wrote: >>> On 29.9.2019 23.38, tovises via dovecot wrote: >>>> I have a quite old home server based on Debian 6.x packages using >>>> courier >>>> imap server (exim4, fetchmail, courier, apache2, squirrelmail) to keep >>>> my >>>> and my wife emails (about 25G). >>>> I want renew

> On 28 Oct 2016, at 16.54, Tanstaafl <tanstaafl at libertytrek.org> wrote: > > On 10/27/2016 8:36 AM, Timo Sirainen <tss at iki.fi> wrote: >> On 27 Oct 2016, at 15:29, Tanstaafl <tanstaafl at libertytrek.org> wrote: >>> On 10/26/2016 2:38 AM, Gandalf Corvotempesta >>>> my only question is: how to manage the email received on the new server

Hi, No, I tried fetching over imapc too exactly as you suggested. In my case it was not from cyrus, but from CriticalPath. isync was finally able to do the job, preserving flags and doing UIDs mapping. The most boring part was generating proper config file for thousands of accounts. A working imapc/dsync would have been better. Emmanuel. Le 26/11/2015 15:24, Sami Ketola a ?crit : > Hi,

> On 28 Sep 2019, at 11:28, Sami Ketola via dovecot <dovecot at dovecot.org> wrote: > > > >> On 28 Sep 2019, at 12.21, Philip Iezzi via dovecot <dovecot at dovecot.org> wrote: >> >> Hi there >> >> We are running Cyrus-to-Dovecot migrations using dsync on destination Dovecot server (Debian Stretch / latest Dovecot 2.3.7.2 from community

Hi there We are running Cyrus-to-Dovecot migrations using dsync on destination Dovecot server (Debian Stretch / latest Dovecot 2.3.7.2 from community repo) like this: $ doveadm -o mail_fsync=never backup -R -u <username> imapc: For imapc configuration to connect to remote Cyrus server, see below [1]. While this works great for hundreds of mailaccounts, dsync fails with the following

Greeting I've managed to backup my emails from external email server via dsync and imapc: protocol like this: doveadm -Dv -o imapc_user='user at gmail.com' -o imapc_password="pass" -o imapc_host=imap.gmail.com backup -R -u duke at ejoom.com imapc: taken from https://wiki.dovecot.org/Migration/Dsync I wish to do regular syncing of 5min interval to substitute

> On 13 May 2018, at 14.07, Matt Bryant <matt at the-bryants.net> wrote: > > Sigh ... ok so had if statement in SQL land that appended LAYOUT=fs if Maildir which explains the non-converting folder layout but NOT why the process is not picking up the actual contents of INBOX ... > Try setting imapc_prefix=INBOX instead of imapc_list_prefix. Sami

Hello, Because it did not work ? In a similar situation, we where forced to use isync/mbsync in imap to imap mode because dsync did not work. It was reported here more than a year ago (May 2014). Time to time, I see the same report from other trying to use dsync to do a migration to dovecot. Dsync is a very appealing and elegant solution to this usage, but it does not always work in real

Hi. When I run the backup I always get this error. ``` [root at mail.DOMAIN.com:~]# doveadm -o mail_fsync=never backup -D -R -u office at DOMAIN.com imapc: dsync(office at DOMAIN.com): Info: imapc(imap.mailbox.org:993): Connected to 2001:67c:2050:106::143:199:993 (local 2a01:4f8:c2c:6d05::1:59928) dsync(office at DOMAIN.com): Info: Mailbox deleted: Drafts dsync(office at DOMAIN.com): Error:

I have been working on converting people from courier maildir -> dovecot mdbox and during some of the dsync runs I'm seeing the quota_exceeded_message be printed as an Error: dsync(<user>): Error: Can't save message to mailbox INBOX: You are over quota. To avoid losing mail, immediately empty your Trash and Sent folders and \ delete emails with large attachments.

I'm using dsync for a regular backup. The backup system flocks so that two cannot run at the same time, which is generally a good thing. The problem is that it seems like dsync sometimes goes off into the weeds and never comes back, leaving a process running and doing nothing forever, hogging the lock and causing my backups never to run again. I just finally figured out that was what was

Sami Ketola wrote:> We run all our migrations using Dovecot internal dsync. Usually using imapc connector to connect to legacy > platform. > > Wqmi Many thanks Wqmi! Well, I've read the dsync documentation, but this warning has me a little worried: "Make sure destination is exactly as source, deleting/reverting any changes in destination if necessary" So I followed

Hi! Kishore, you got the command wrong.. `doveadm backup -R -u username-goes-here imapc:` for this to work, you need to configure following things: imapc_host = old-host-name imapc_password = master-password imapc_master_user = master-user-name and on the old host you need passdb { args = /etc/dovecot/passwd.masterusers driver = passwd-file master = yes pass = yes } This should

On 27 Oct 2016, at 15:29, Tanstaafl <tanstaafl at libertytrek.org> wrote: > > On 10/26/2016 2:38 AM, Gandalf Corvotempesta > <gandalf.corvotempesta at gmail.com> wrote: >> This is much easier than dovecot replication as i can start immedialy with >> no need to upgrade the old server >> >> my only question is: how to manage the email received on the

https://dovecot.org/releases/2.2/rc/dovecot-2.2.31.rc1.tar.gz https://dovecot.org/releases/2.2/rc/dovecot-2.2.31.rc1.tar.gz.sig Unless new bugs are found, this will be the final v2.2.31 release, which will be released on Monday. * LMTP: Removed "(Dovecot)" from added Received headers. Some installations want to hide it, and there's not really any good reason for anyone to