similar to: Syncing shared mailboxes

Hi, I recently upgraded to openSuse 12.1 which comes with dovecot 2.0.14. Because of mail-client-problems I am running one dovecot which requires authentication via a client-certificate and another one which can be used without a certificate. (Configurations can be found below.) Since the upgrade our shared mailbox is no longer visible. I tried to repair this by setting the ACLs once again (using

Hi there, We're trying to convert users from Maildir to sdbox at present; I'm using dsync to achieve this (2.0.16) however when the user's have been converted we only get minimal information in the caching files. Is there some way to preserve all the caching decisions that were previously made so that when the user logs in to the new mailbox we don't have to cause an io storm

Hi all, lets say I've registered at several Sip-Providers. Provider A offers best rates but is often too busy to get a line. Sip Provider B is stable (but more expensive). The asterisk box has a high call volume therefore problems at provider A will get obvious after a few calls stalled. In this case astersik shall switch temporarily to provider B but shall test periodically for selected

doveadm already supports some nice things, such as being able to remotely launch a doveadm command via TCP socket. It also supports executing a command for all users or to some specific users using a wildcard. dsync could use these features, so I merged dsync and doveadm into same binary for v2.1. I'll still install "dsync" symlink pointing to "doveadm", and running that

Gents, I'm relocating mailboxes to a new server. Before switching over to a new server I ran syncing a few times without any issues first I sync files with rsync from the old server to have a local copy, then I sync mailboxes with dsync /usr/bin/doveadm -Dv sync -u $MBOX -R "sdbox:/srv/vmail/temp/srv/srv.bgoperator.ru/${MBOX}:DIRNAME=DbOx-mAiLs" After switching over smtp

Hi list, I recently tried to backup mailboxes from an older server machine to a new one in order to move the service to the new machine. Both machines are in the same LAN, I used this command: dsync -R -u username backup ssh -i .ssh/id_rsa username at 192.168.1.11 /opt/local/bin/dsync and I get this error: dsync-local(dz): Error: Invalid server handshake: dsync-server 2 dsync-remote(dz):

Greetings, We have about 26 GB of email which we're trying to sync nightly to a remote server, but what I just read from a post from Timo awhile back is that it's not possible because dsync relies on message GUIDs which aren't available in the IMAP protocol. It seems that this is still the case, is there anything on the horizon for this to change? -- *Asai* Global Change

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.1/dovecot-2.1.2.tar.gz http://dovecot.org/releases/2.1/dovecot-2.1.2.tar.gz.sig There are a ton of proxying related improvements in this release. You should now be able to do pretty much anything you want with Dovecot proxy/director. This release also includes the initial version of dsync-based replication. I'm already successfully using it for @dovecot.fi

http://dovecot.org/releases/2.1/dovecot-2.1.2.tar.gz http://dovecot.org/releases/2.1/dovecot-2.1.2.tar.gz.sig There are a ton of proxying related improvements in this release. You should now be able to do pretty much anything you want with Dovecot proxy/director. This release also includes the initial version of dsync-based replication. I'm already successfully using it for @dovecot.fi

http://dovecot.org/releases/2.1/beta/dovecot-2.1.beta1.tar.gz http://dovecot.org/releases/2.1/beta/dovecot-2.1.beta1.tar.gz.sig Here's the first beta release of Dovecot v2.1. This version has already been tested quite a lot, so I'm not expecting any major bugs. So please upgrade and see if you can find any problems. I'm optimistic about getting rc1 released this year and perhaps even

http://dovecot.org/releases/2.1/beta/dovecot-2.1.beta1.tar.gz http://dovecot.org/releases/2.1/beta/dovecot-2.1.beta1.tar.gz.sig Here's the first beta release of Dovecot v2.1. This version has already been tested quite a lot, so I'm not expecting any major bugs. So please upgrade and see if you can find any problems. I'm optimistic about getting rc1 released this year and perhaps even

I've got the ztdummy kernel module loaded and seem to have all the desired prerequisites in place, but Asterisk never seems to compile with MeetMe() application support enabled, nor does there appear to be a module I am failing to load that would contain this application. Is there something really obvious I am missing? Thanks, -- Alex Balashov Evariste Systems Web :

Hello, Here is a Panic that happened while doing some testing with two servers both running Dovecot v2.2.26 on CentOS 7. These are test servers owning 32 accounts whose data were copied from our production server. What I've done is: server01# doveadm force-resync -A '*' server01# doveadm replicator replicate -f '*' For 5 accounts I obtained the following crash:

I'll release v2.1.rc6 in maybe 16 hours or so. If no problems are reported in it after a few days I'll just change version to 2.1.0. So now's a great time to try the latest v2.1 hg version to see if there are any problems. I've gone through all of my old mails. Let me know if you think something is still missing / unfixed in v2.1 hg. Preferably today. Next up: Creating

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

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

Dovecot 2.1.7 While migrating mail from one server (Maildir) to another (mdbox), a config issue caused my dsync to fail on a few accounts. Those accounts received mail on the new server over night and it autocreated new inboxes with new GUIDs. Now dsync wants nothing to do with mirroring between the two (diff GUIDs). Is there a way to fix this? dsync(jeff at foo.bar): Error: Mailbox INBOX

Hello, I'm in the process of migrating mailbox from one dovecot server running dovecot 2.1.9 with mailboxes stored in maildir format to a newer one running 2.1.16 with mailboxes stored in mdbox format. To migrate mailboxes I'm using dsync as explained at http://wiki2.dovecot.org/Tools/Dsync. The command I'm running in the newer server is: sudo dsync -o mailbox_list_index=no