similar to: Migrating Emails from 1.0.15 to 1.2.2

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

On Mon, 13 Jul 2020 10:50:09 +0200 Robert Schetterer <rs at sys4.de> wrote: > perhaps this help > > getmail should use /usr/lib/dovecot/deliver That is what I used before and wanted to switch off. Here is the 2 main reasons: 1) It add extra header overhead similar to: Received by localost at time, etc....) 2) It put emails in local delivery queue so syncing becomes slow. 3)

Imapsync for sure. Have used it for both IMAP to IMAP and IMAP to Exchange migrations. Works great. > On Dec 3, 2017, at 2:08 PM, x9p <dovecot at x9p.org> wrote: > > Hi, > > I vouch for imapsync. Have used it in the past with quite a big amount of > emails. > > cheers. > > x0p > >> Hi Friends, >> I would like to ask you a suggestion:

Hi Friends, I would like to ask you a suggestion: I need to migrate a imap server to a new one and then dismiss the old one. Reading from relative Dovecot documentation page (https://wiki.dovecot.org/Migration), more tools are shown: UW-IMAP's mailutil, imapsync, YippieMove and Larch. The each mail servers are Linux based, one of this (mine) is Dovecot. Based on your experience which of

> 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

On Mon, Dec 4, 2017 at 9:16 AM, Sami Ketola <sami.ketola at dovecot.fi> wrote: > > With every other tool you will face end users needing to invalidate their > local caches and > redownloading all headers if not also all mail bodies. > > Sami > > I don't think so. Been using imapsync for large scale migrations from external servers to our dovecot setup. Users

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 Tue, Dec 5, 2017 at 4:16 AM, Sami Ketola <sami.ketola at dovecot.fi> wrote: > On Mon, Dec 4, 2017 at 9:16 AM, Sami Ketola <sami.ketola at dovecot.fi> > wrote: > >> >> With every other tool you will face end users needing to invalidate >> their local caches and >> redownloading all headers if not also all mail bodies. >> >> Sami

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

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, I'm using Imapsync to sync messages from an Exchange 2003 server to a Dovecot 1.1.11 server. The problem is that users' mailboxes are huge, several gigabytes with tens of thousands of messages. First Imapsync connects to Exchange and then to Dovecot, and then starts to get Inbox info from Exchange. By the time it gets this info, the connection to Dovecot has timed out. I realize the

Dear dovecot list, I'm using Maildir as mailbox format. Is there any recommendation for the namespace hierarchy separator? Currently I didn't set any. So it is the default of dot '.' I'm switiching from a rather unknown IMAP Server called DBMail (http://www.dbmail.org/) Planning to synchronize the mailboxes via imapsync (https://github.com/imapsync/imapsync) Is there

Could you help me trouble shoot this? I am a bit of a rookie and probably screwed something up. I am trying to "make" imapsync, but there is a complaint regarding some Perl problem that I cannot figure out. [root at testmail imapsync-1.182]# make Use of uninitialized value in concatenation (.) or string at /usr/lib/perl5/5.8.5/i386-linux-thread-multi/Scalar/Util.pm line 30. is

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,

I'm about to replace my old server. Both servers are on my internal network. The old one ist running debian lenny(32bit) with dovecot 1.0.15 and the new one debian Wheezy with dovecot 2.1.7. I set up the users on both systems identically (same gid uid). My first attempt was tho simply rsync the Maildirs along with the homes. Both deovecot versions are set up with the maildir format, but this

I;m setting up new server, what are the options for transferring user's mail ? I've tried imapsync, that seems to work well, but, what options do I have for doing accounts or domains where I don't know user's password ? last time I've done, some users had lengthy period of re downloading 'old' mails from new server, is there a way to overcome this ? thanks, V

Il 2017-12-05 07:16 Sami Ketola ha scritto: [..] > > Trust us. We have run multiple migrations at scale of 10+ million > users. > > Sami However, it seems that Imapsync has license issues and in fact it's not included in the Debian repositories. Is it to be used anyway or should be avoid? Many thanks again Davide

The dot '.' will work, but I suggest to follow documentation here: https://wiki1.dovecot.org/Namespaces, And it says: A commonly used separator is '/'. It probably causes the least amount of trouble with different IMAP clients And I already had problems using '.' as a namespace separator. On 2020-04-24 15:56, Sami Ketola wrote: > >> On 24. Apr 2020, at

hello list, I am attempting to sync two imap servers using the imapsync perl script. It seems handy and easy. Here's what happens when I try to do this: # # Postfix master process configuration file. For details on the format # of the file, see the master(5) manual page (command: "man 5 master"). # -o smtpd_sasl_auth_enable=yes # -o

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