similar to: Migrate to new server without raw copy

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

Thank you for the reply. I did find imapsync whilst perusing Google. I will give it a shot, it sounds more realistic/reliable. I have a hoard of emails going back to 1999, so I want as few errors as possible :) On 11/7/15 3:31 PM, Philon wrote: > Hi there, > > I was in the same position, but for mutliple accounts. Still you might want to look at imapsync

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

Hi All! I am working on a complete migration from an old solaris machine running Cyrus IMAP v2.3.14 and wish to migrate all users to a new ubuntu vm running Dovecot 2.0.19. What I have so far is a fully functional dovecot installation with LDAP / Dovecot SASL auth using Maildir++. My plan is to use Perdition IMAP proxy on a third host and migrate users a few at a time (see attached picture of

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

On 23/01/16 15:33, Robert Schetterer wrote: > for multiple advanced imap settings at migration you might use > imapsync not dsync Best Regards MfG Robert Schetterer Sure but imapsync does not preserve message UID's which means that users end up redownloading all their messages or message/UID mismatches will happen. Sami

Am 04.09.2018 um 18:27 schrieb Sami Ketola: > > >> On 4 Sep 2018, at 18.38, Robert Schetterer <rs at sys4.de> wrote: >> >> Sorry i migrated terrabytes of mail with imapsync and never had a >> problem, it works as designed, also with maildir rsync did a good job, >> what never worked as it should was dsync ,cause of bugs ,that may >> changed now

I've completed my mailbox rebuild - theoretically I should be free of corruption. I used dsync to export from mdbox to maildir (so should be clean) then used a virtual machine with Dovecot to import back to mdbox in another location. So...theoretically I should be free of all corruption now... Running an fts update - "doveadm search text -u user at domain.com xyzzyx" works on

> 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

Am 04.09.2018 um 17:18 schrieb Sami Ketola: > > >> On 4 Sep 2018, at 18.00, Robert Schetterer <rs at sys4.de> wrote: >> >> Am 04.09.2018 um 16:52 schrieb Sami Ketola: >>> >>> >>>> On 4 Sep 2018, at 17.47, Robert Schetterer <rs at sys4.de> wrote: >>>> >>>> Am 04.09.2018 um 09:41 schrieb Sami Ketola:

> On 7. Jun 2020, at 18.20, John Stoffel <john at stoffel.org> wrote: > >>>>>> "Gingko" == Gingko <ldiff001 at gingko.ovh> writes: > > Gingko> I also have issues using Dovecot Backup. > > Gingko> I am trying to Backup (or possibly Sync - one way) a single > Gingko> user IMAP account from a remote server, unknown type, to my

It's apparent I have some level of corruption in my mailboxes - something to do with the combination of mdbox, sis, and zlib. I should note that I know I have a mix of compressed and raw messages - if that makes any difference in identifying the problems. I think I need to somehow regenerate the mailboxes with issues. Is there a suggestion for how to accomplish this? Should I perhaps use

Hi, I am looking for tools to migrate Mails from one IMAP-Server to another. Until now I have always used imapsync, but it seems very slow. Even over a 2x10GB/s connection I only get speeds of about 600KiB/s, because the programm always pauses betweeen every single mail. Does anyone here have a suggestion for an alternative? Thanks in advance Julian

Am 05.09.2018 um 07:37 schrieb Aki Tuomi: > >> On 04 September 2018 at 23:20 Robert Schetterer <rs at sys4.de> wrote: >> >> >> Am 04.09.2018 um 18:27 schrieb Sami Ketola: >>> >>> >>>> On 4 Sep 2018, at 18.38, Robert Schetterer <rs at sys4.de> wrote: >>>> >>>> Sorry i migrated terrabytes of mail with

Hi All, I currently have a small Dovecot server (Server A) and I've installed a second dovecot mailbox server (server B) and am trying to sync mailboxes from Server A to Server B. Both servers sit behind two dovecot directors on separate hosts and have identical config files (doveconf -n output below). Mailboxes on Server A are on an NFS mount. Server A has been working fine with no

> On 26 Jan 2016, at 15:56, Marc Schiffbauer <m at sys4.de> wrote: > > * Sami Ketola schrieb am 23.01.16 um 23:27 Uhr: >> >> >> On 23/01/16 15:33, Robert Schetterer wrote: >>> for multiple advanced imap settings at migration you might use >>> imapsync not dsync Best Regards MfG Robert Schetterer >> Sure but imapsync does not preserve

Hi, I'm still trying to migrate from Dovecot 1.2.16 to 2.0.7 on FreeBSD. Previous attempts have failed with mails not being visible after the upgrade. Version 1.2.16 was migrated from maildir to dbox about a year ago via the convert-plugin. After previous attempts to "clean" the hybrid maildir-dbox situation I used imapsync to copy all mails from the old account to a new

Hello list, im am trying to migrate customer mails via dsync from an old dovecot 1.1 setup to an new installed dovecot 2.2.25 setup with mdbox. Upgrading the old dovecot 1.1 to 2.2 with Maildir isnt an problem and the replication to the new setup works well too. The only problem now is, that the POP3 UIDL are completely wrong on the target setup. Im using for Maildir pop3_uidl_format = %f With

Hello, I'm in the process of migrating accounts between two dovecot servers. An old server running ancient 1.0.15 and a new server running 1.2.15. Account migration is going to be gradual and so i would like to use imapsync to move messages and subscriptions from one server to the other. The only problem so far is with POP users. After doing an account migration with imapsync, and