similar to: Dsync clustering

Hello List, i only found an old post of tiemo where he announced that he will do an wiki article how to setup dovecot cluster with dsync over ssh. anyone knows if this artcile exists and where? i would like to setup a dovecot cluster with 2 machines. thanks for help marko

http://dovecot.org/releases/2.2/rc/dovecot-2.2.rc2.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.rc2.tar.gz.sig Looks like the last changes I did today just before rc1 release made it just about unusable. This one is actually running on my servers. :)

http://dovecot.org/releases/2.2/rc/dovecot-2.2.rc2.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.rc2.tar.gz.sig Looks like the last changes I did today just before rc1 release made it just about unusable. This one is actually running on my servers. :)

More dsync issues. We were running 2.1.7 and we updated to 2.1.9. Same problem with both versions. I'm getting an error 75 on about 40 boxes out of 1800. It is the same list of boxes every time we use 'dsync backup' to backup the server. dsync seems to stop communicating to the backup box (over ssh). strace just shows it sitting at a epoll_wait. Once the program quits (times out?), a

I have been loosely following discussions dsync replication, but I am wondering if this tool still in a testing phase or has it been committed as a production part of Dovecot? I would like to do some testing with the protocol to see if it's capable of handling the change rate our mail service generates, which has about 23,000 active users. We are trying to find solutions for a two site

Hello, I have an intermittent but frequent problem using dsync backup. The command outputs: dsync-local(user): Error: proxy client timed out Then dies with exit code 75. Any subsequent attempts to re-run the backup invariably fail like this: dsync-local(user): Warning: Destination mailbox INBOX has been modified, need to recreate it before we can continue syncing dsync-local(user): Error:

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

I just tried to migrate one of my users from maildir to mdbox using dsync. My conversion script is checking the dsync exit code to know if the conversion goes fine or not, and surprisingly dsync returned "0" at the same time as it gave the error: Error: Failed to sync mailbox .ta\ vare\ p? ... (sorry, lost the rest of the error message) Changing the folder name to mUTF7 manually

According to the roadmap http://wiki2.dovecot.org/Roadmap implementation of the METADATA / ANNOTATE extensions is fairly high on the list. I was just curious if there is a target release in mind for this functionality?

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,

http://dovecot.org/releases/2.2/beta/dovecot-2.2.beta1.tar.gz http://dovecot.org/releases/2.2/beta/dovecot-2.2.beta1.tar.gz.sig Lots of fixes since 2.2.alpha1, especially related to dsync. Also dsync now supports syncing private message flags when INDEXPVT is used. Here's again the list of all the major changes in v2.2: * When creating home directories, the permissions are copied from the

http://dovecot.org/releases/2.2/beta/dovecot-2.2.beta1.tar.gz http://dovecot.org/releases/2.2/beta/dovecot-2.2.beta1.tar.gz.sig Lots of fixes since 2.2.alpha1, especially related to dsync. Also dsync now supports syncing private message flags when INDEXPVT is used. Here's again the list of all the major changes in v2.2: * When creating home directories, the permissions are copied from the

Dear all I have a few public folders setup and working fine, and one such public folder is 'Public/General'. I'm trying to sort dsync replication out to another server and notice that the system log is full of error messages similar to: dovecot: doveadm: Error: dsync-remote(username: Error: Can't update subscription Pu blic/General: Invalid mailbox name The replication setup

http://dovecot.org/releases/2.2/beta/dovecot-2.2.beta2.tar.gz http://dovecot.org/releases/2.2/beta/dovecot-2.2.beta2.tar.gz.sig A ton of fixes since beta1. Especially the new dsync and the replication server related to that should really work now. It also works correctly now for shared mailboxes with private \Seen flags. And the replication server uses incremental syncing after the initial full

http://dovecot.org/releases/2.2/beta/dovecot-2.2.beta2.tar.gz http://dovecot.org/releases/2.2/beta/dovecot-2.2.beta2.tar.gz.sig A ton of fixes since beta1. Especially the new dsync and the replication server related to that should really work now. It also works correctly now for shared mailboxes with private \Seen flags. And the replication server uses incremental syncing after the initial full

Hi, It seems that dsync 2.1.10 does not correctly handle renames of mailbox subtrees. The scenario is as follows. There are two servers, A and B, both running dovecot 2.1.10 and configured to use mdbox. Automatic replication between them is disabled, ie. replication plugin is not active and replicator service has process_min_avail = 0. I perform the following actions: 1. On A: doveadm mailbox

http://dovecot.org/releases/2.2/dovecot-2.2.0.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.0.tar.gz.sig Everything now seems to be stable and working in v2.2, so I can finally move onto developing great new interesting features for v2.3. :) My company has also launched a web shop where you can buy various products. One of them is cheap access to Dovecot enterprise edition repositories,

http://dovecot.org/releases/2.2/dovecot-2.2.0.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.0.tar.gz.sig Everything now seems to be stable and working in v2.2, so I can finally move onto developing great new interesting features for v2.3. :) My company has also launched a web shop where you can buy various products. One of them is cheap access to Dovecot enterprise edition repositories,

http://dovecot.org/releases/2.2/dovecot-2.2.3.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.3.tar.gz.sig This is a pretty important upgrade for v2.2 users, because of the IMAP ENVELOPE reply fix. * LDA/LMTP: If new mail delivery first fails with "temporary failure", tempfail the whole delivery instead of falling back to delivering the mail to INBOX. (Requires new Pigeonhole

http://dovecot.org/releases/2.2/dovecot-2.2.3.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.3.tar.gz.sig This is a pretty important upgrade for v2.2 users, because of the IMAP ENVELOPE reply fix. * LDA/LMTP: If new mail delivery first fails with "temporary failure", tempfail the whole delivery instead of falling back to delivering the mail to INBOX. (Requires new Pigeonhole