similar to: dbox: maildir migration

Ok... Now that I've got the niggling issues resolved, on to bigger and better things. I want to convert everyone from Maildir to dbox and enable SIS (our users use a lot of large attachments), and after some reading/googling, I think it may be better to use dsync instead of rsync for the actual migration after all since it will do this at the same time as the syncing. If I'm not

Hi, I'm trying to migrate from Dovecot 1.2.16 to 2.0.7. Initially the mails were stored in Maildir format but I changed them to dbox using "fast Maildir migration" and some mails are still in the old maildir format. I'm trying to migrate these mails using dsync but dsync panics: % dsync -D -o mail_location=dbox:/var/spool/vmail/bunbun.be/nick mirror

Ok, now to work out the precise method (config for the target server and dsync command) to use to perform the migration from the old server to the new one, converting to dbox (s or m, depending on how the other thread discussing this turns out). I'll update the old server to 2.2.10 tomorrow morning so they're both at the same version. So, assuming both servers are running 2.2.10,

It has been my wish to move to dbox for a long time hoping to reduce the number of writes which is really killing us. Now I wonder what may be the best way of doing so. I'm considering some sort of intermediate migration where the existing Maildir users are changed to single-dbox and then later upgraded to 2.0 and changed to multi-dbox when it becomes stable. But is this a reasonable task

Hi! I've changed my mailbox format from dbox to Maildir. The problem is maildir message filename extension has no S=/W= field after migration. Using dovecot 2.1.15.

Hi all, a dsync failed due a corrupted mdbox file. Force-resync throws the same error. (Dovecot 2.3.9.2) Is there any change to fix/repair the file? dsync-local(LOCALPART at DOMAIN.TLD)<MBF5EUC8j1/FfQAAkqONGQ>: Warning: fscking index file /var/mail/12/DOMAIN.TLD/242/LOCALPART/mdbox/storage/dovecot.map.index dsync-local(LOCALPART at DOMAIN.TLD)<MBF5EUC8j1/FfQAAkqONGQ>: Warning:

Hello, So ive spent the last 45 minutes or so searching the list for dbox stuff, but Im not seeing anything real definitive. My question is basically whether the dbox format is ready for production environment, is sdbox or mdbox more stable/ready than the other or does it matter? What are people's experience/review with running this format (and if you reply can you tell me which one

Ok - I gave up on trying to get CIFS to work - there's obviously stuff going on I don't understand. So - instead of trying to get a virtual server to work, I next tried a chroot. That worked...but imapsync error'ed out trying to handle one of my large mailboxes. I was trying to setup a "new" server, migrate all my mail over, verify everything worked - maybe even leave the

http://dovecot.org/releases/2.0/rc/dovecot-2.0.rc1.tar.gz http://dovecot.org/releases/2.0/rc/dovecot-2.0.rc1.tar.gz.sig All of the important features are implemented and all of the important bugs are fixed. The only thing I'd like to solve before v2.0.0 is that two people have said their doveconf fails when trying to convert old v1.x config file. I haven't been able to reproduce this, so

http://dovecot.org/releases/2.0/rc/dovecot-2.0.rc1.tar.gz http://dovecot.org/releases/2.0/rc/dovecot-2.0.rc1.tar.gz.sig All of the important features are implemented and all of the important bugs are fixed. The only thing I'd like to solve before v2.0.0 is that two people have said their doveconf fails when trying to convert old v1.x config file. I haven't been able to reproduce this, so

I migrated from existing dovecot Maildir to dbox. After adding separator to the namespace it migrated all Inbox mails, but the other mailboxes like user-created ones and "Junk", "Sent" and so on has not been migrated. Any advice would be helpful, here is my dovconf: https://pastebin.com/rDSeBcLe My migration I made using: 1. Edit dovecot.conf with new mdbox and adding

And /bin/doveconf namespace namespace { disabled = no hidden = no ignore_on_failure = no inbox = no list = children location = mdbox:/var/mailboxes/%%2Mu/%%2.2Mu/%%u order = 0 prefix = shared/%%u/ separator = / subscriptions = yes type = shared } namespace inbox { disabled = no hidden = no ignore_on_failure = no inbox = yes list = yes location = mailbox Drafts

Hi After http://retrospekt.dk/2011/08/migrating-maildir-to-dovecot-2-0-dbox/ I used a two phases process. The first, transfering over the network, is done by this shell function, on the *new* server. The argument is the <user> fetchOldServer () { rsync -poazuHK --exclude="**/dovecot.index*" \ -e ssh root at oldServer:/var/mail/Maildirs/$1 /var/mail/oldServer/ } I had

Hello Actually we use MBOX format for all our IMAP access but users complain they cannot create subfolders in imap folders, of course they cannot because of MBOX format ... I need gurus advices on changing mailbox format Maildir of Dbox ? What would be the safest way to go ? Note : we extensively use Thunderbird here. Thanks

Ok...I made the leap. Compiled a copy of 1.2b4 (very pleasant compile BTW - almost no warnings, nice code Timo!)...tweaked a config...had a few false starts... 1.2b4 seems to working quite nicely. Now...for my next magical trick... I would like to migrate from maildir to dbox. I've tried using the convert plugin, but it kept failing during the conversion. I should mention my paths:

http://dovecot.org/releases/2.0/rc/dovecot-2.0.rc3.tar.gz http://dovecot.org/releases/2.0/rc/dovecot-2.0.rc3.tar.gz.sig A lot of dsync fixes. I think I've fixed now all of the bugs ever reported about dsync and I'm hopeful that it's now stable. All the rest of Dovecot looks pretty good too. Maybe v2.0.0 will be out next week. Changes since rc2: * Single-dbox is now called

http://dovecot.org/releases/2.0/rc/dovecot-2.0.rc3.tar.gz http://dovecot.org/releases/2.0/rc/dovecot-2.0.rc3.tar.gz.sig A lot of dsync fixes. I think I've fixed now all of the bugs ever reported about dsync and I'm hopeful that it's now stable. All the rest of Dovecot looks pretty good too. Maybe v2.0.0 will be out next week. Changes since rc2: * Single-dbox is now called

http://dovecot.org/releases/2.0/dovecot-2.0.4.tar.gz http://dovecot.org/releases/2.0/dovecot-2.0.4.tar.gz.sig multi-dbox users: Be careful about the INDEX change. Maildir users: I hope v2.0 is now finally stable. * multi-dbox: If :INDEX=path is specified, keep storage/dovecot.map.index* files also in the index path rather than in the main storage directory. WARNING: if you specified

http://dovecot.org/releases/2.0/dovecot-2.0.4.tar.gz http://dovecot.org/releases/2.0/dovecot-2.0.4.tar.gz.sig multi-dbox users: Be careful about the INDEX change. Maildir users: I hope v2.0 is now finally stable. * multi-dbox: If :INDEX=path is specified, keep storage/dovecot.map.index* files also in the index path rather than in the main storage directory. WARNING: if you specified

After a filesystem crash dovecot isn't able to repair some of the m-Files. That's okay in general -- but I wonder why he's complaining about "wrong dsync version" if I execute "doveadm force-resync" locally: doveadm(user at mailbox.org): Warning: mdbox /mail-mailbox/mailbox.org/1846405//mdbox/storage: rebuilding indexes doveadm(user at mailbox.org): Error: