similar to: Safe to run migration on live/production server?

On 2016-10-25 06:51, Aki Tuomi wrote: > On 25.10.2016 09:43, mrobti at insiberia.net wrote: >> I have inherited a 10+ GB mailbox which dsync converted to maildir >> very nicely. But 15GB in tens of thousands of messages is too much in >> one INBOX when used in webmail. >> >> I guess it's best to divide the messages into subfolders for date. >> >>

I have inherited a 10+ GB mailbox which dsync converted to maildir very nicely. But 15GB in tens of thousands of messages is too much in one INBOX when used in webmail. I guess it's best to divide the messages into subfolders for date. Is there a server-side way to safely move messages into new subfolders so that Dovecot indexes and UIDs won't break? If I write a shell script to move

We are currently in the process of replacing one of our customer mail systems with a dovecot solution. However, one of the sticking points right now is how to get the old mail to the new system. On the dovecot side, we are using mdbox storage. On the old system we are using qpopper/mbox mailboxes in the following setup. All user inboxes are in /mnt/mail/mail_spool. Only select, privileged,

On 25.10.2016 09:43, mrobti at insiberia.net wrote: > I have inherited a 10+ GB mailbox which dsync converted to maildir > very nicely. But 15GB in tens of thousands of messages is too much in > one INBOX when used in webmail. > > I guess it's best to divide the messages into subfolders for date. > > Is there a server-side way to safely move messages into new subfolders

Dear list, dovecot version: 2.1.7 I have an old mail server that uses mboxes for the INBOX and maildirs for subfolders. I want to migrate our mail handling to a new setup using mdboxes for everything. The current config looks like this: # 2.1.7: /etc/dovecot/dovecot.conf doveconf: Warning: service anvil { client_limit=1000 } is lower than required under max. load (1127) # OS: Linux

Hello, I am planning to migrate all users from mbox to maildir. I am trying to do it with minimum downtime. (~100GB data) All users are currently using POP3. Dovecot version is 2.2.10 (latest). Command used is: dsync -u username mirror maildir:~/Maildir Process I plan is: (omitting steps related to sendmail / procmail) 1) keep dovecot running (with mail_location as mbox) 2) dsync for all

Hi again, after replacing CRLF in 4 mboxes dsync was able to sync all of the 30+GB mailstore to mdbox. Now the (repeated) calling of dsync yields info messages of the kind dsync(athimm): Info: old/speicher: highest_modseq changed: 1 != 10 dsync(athimm): Info: root/root-heretic: highest_modseq changed: 1 != 10 dsync(athimm): Info: lists/ccrma.stanford.edu/planetccrma: highest_modseq changed: 11

I am about to be migrating mail servers and have a few questions. First a little background: Old mail server: Fedora 11 dovecot-1.2.11-3.fc11.x86_64 installed from yum repo mbox mail format OpenLDAP authentication 250+ users New mail server: Fedora 13 dovecot-2.0.1-1_118.fc13.x86_64 installed from atrpm rpm file Maildir mail format OpenLDAP authentication 250+ users I plan to use dsync on the

Hi Timo, using http://wiki2.dovecot.org/Migration/Dsync for migration i am getting this in periods dsync(sys4-test-2 at example.de): Info: INBOX: Couldn't keep all uids dsync(sys4-test-2 at example.de): Warning: Mailbox changes caused a desync. You may want to run dsync again. dsync(sys4-test-2 at example.de): Warning: I/O leak: 0x756547164490 (line 1229, fd 15) dsync(sys4-test-2 at

Hi all, I think it would be a good idea for me to move from mbox to mdbox, as I have 57,000 messages in my inbox, and clients hang for a minute whenever they request a CHECK, or Dovecot feels the need to run one itself. Looking at past threads: http://www.mail-archive.com/dovecot at dovecot.org/msg35212.html http://comments.gmane.org/gmane.mail.imap.dovecot/53936 it seems that the safest way

Dear all i'm planning a transparent migration from a courier server that provides both IMAP and POP3 access to users to a remote dovecot server with both IMAP and POP3 access. I have to migrate about 2500 users for 250 GB of space. I'm using dovecot 2.2.5.4 on debian6 squeeze. To make a transparent migration i have to maintain old IMAP UIDs and POP3 UIDs, so i've read

I finally migrated my mails from mbox format to mdbox format using dsync: 1. Stop dovecot, wait a few seconds for processes to die 2. dsync convert mdbox:~/mdbox 3. Change mail_location to mdbox:~/mdbox 4. Check that no new mails arrived during conversion (alternatively I could have just run dsync again, but I decided not to test my luck) 5. Start dovecot After fixing a pretty bad bug in dsync

As part of my current research for upcoming setup, I started reading up on filesystems (was actually looking up fencing which leds to node crash and file integrity on different fs) to see if there would be any significant improvement to using a different filesystem for networked storage. e.g. glusterfs on top of ext4 nodes. Initially, the reading suggested that ext4 would provide a significant

Hi I am new to the mailing List, and was hoping to get some assistance migrating from an Old Cucipop + Sendmail server (running on a old Redhat v 7) to a new Dovecot setup. My new installation is Dovecot + Postfix. All is setup and working, however I want to trasnsfer the contents of the mailboxes from my old server to this new Dovecot setup. Please let me know what information will be required

Dovecot v2.1 hg (http://hg.dovecot.org/dovecot-2.1) now supports doing e.g.: dsync -o plugin/imapc_user=remote.user at example.com -o plugin/pass=remote-password mirror imapc:imap.example.com dsync will preserve message UIDs and UIDVALIDITY/UIDNEXT values for mailboxes, just like with all other storage backends. A couple of bad things: 1) It currently fetches one message at a time from server.

Hi, with 2.2.2 and today's hg, dsync crashes with dsync(root): Panic: file ../../../../../src/lib-storage/index/mbox/mbox-lock.c: line 797 (mbox_lock): assertion failed: (lock_type == F_RDLCK || mbox->mbox_lock_type != F_RDLCK) when I run USER=root 2.2-hg/bin/dsync -c etc/dovecot.conf -f -o mail_location=mbox:/tmp/imap/fwadmin.tmp:INBOX=/tmp/imap/fwadmin.tmp/INBOX mirror

Hi, I'm trying to convert a 33GB mail store from mbox to compressed mdbox (largest mbox is 2.7GB). The source store is live, e.g. there are mails delivered into it and mails are being read. Actually it is my own mail. :) Although my test runs were very successful I have run into trouble with the first run on the whole store. After fighting a bit around with errors like Error: Trying

Am 24.10.2016 um 09:00 schrieb Gandalf Corvotempesta: > Hi > i have to migrate, online, a dovecot 1.2.15 to a new server. Which is the > best way to accomplish this? > > I have 2 possibility: > 1) migrate from the very old server to a newer server with the same dovecot > version > 2) migrate from the very old server to a new server with the latest dovecot > version >

Hi all, virsh checks whether a (live) migration is safe or unsafe. When a migration is considered to be unsafe it is rejected unless the --unsafe option is prodivided. As a part of those checks virsh considers the cache settings for the underlying storage resources. In this context only cache="none" is considered to be safe. I wonder why cache="directsync" might be harmfull

I'm trying to convert from an old Dovecot (1.0.15) and mbox to a new Dovecot and maildir. I'm running into several problems with dsync which are causing my mboxes not to convert. If I use LAYOUT=fs (as I'd prefer) I get an error because I have a mailbox called "subscriptions", and none of my messages convert. Is there a way to get dovecot to put its own metadata in