similar to: v2.2.rc3 released

http://dovecot.org/releases/2.2/alpha/dovecot-2.2.alpha1.tar.gz http://dovecot.org/releases/2.2/alpha/dovecot-2.2.alpha1.tar.gz.sig I wanted to start stabilizing v2.2 release some months ago already, but I somehow got stuck adding more and more features. Now it looks like all of the necessary API changes are done, so everything I'm planning on near future can still be added to v2.2 without

http://dovecot.org/releases/2.2/alpha/dovecot-2.2.alpha1.tar.gz http://dovecot.org/releases/2.2/alpha/dovecot-2.2.alpha1.tar.gz.sig I wanted to start stabilizing v2.2 release some months ago already, but I somehow got stuck adding more and more features. Now it looks like all of the necessary API changes are done, so everything I'm planning on near future can still be added to v2.2 without

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

http://dovecot.org/releases/2.2/rc/dovecot-2.2.rc1.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.rc1.tar.gz.sig A few fixes since beta2. Also added tcp and tcps (=tcp+ssl) targets for dsync, where the destination needs to be a doveadm-server listener. I'm planning on releasing v2.2.0 in 1-2 weeks if no major problems are found. Please test and report any bugs found. BTW. I've

http://dovecot.org/releases/2.2/rc/dovecot-2.2.rc1.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.rc1.tar.gz.sig A few fixes since beta2. Also added tcp and tcps (=tcp+ssl) targets for dsync, where the destination needs to be a doveadm-server listener. I'm planning on releasing v2.2.0 in 1-2 weeks if no major problems are found. Please test and report any bugs found. BTW. I've

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.2/rc/dovecot-2.2.rc4.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.rc4.tar.gz.sig A lot of small random fixes. Some last minute major cleanups/fixes to lib-http and lib-ssl-iostream error handling, which makes them much easier to debug if something goes wrong (so e.g. if https site has invalid certificate, the caller gets error message saying that, including

http://dovecot.org/releases/2.2/rc/dovecot-2.2.rc4.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.rc4.tar.gz.sig A lot of small random fixes. Some last minute major cleanups/fixes to lib-http and lib-ssl-iostream error handling, which makes them much easier to debug if something goes wrong (so e.g. if https site has invalid certificate, the caller gets error message saying that, including

http://dovecot.org/releases/2.2/rc/dovecot-2.2.rc6.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.rc6.tar.gz.sig Some more fixes to bugs I noticed today while trying out some new things in production. Note especially the replicator-doveadm socket change, see http://wiki2.dovecot.org/Replication for how to configure it. This change allowed local replicator to notify the remote replicator

http://dovecot.org/releases/2.2/rc/dovecot-2.2.rc6.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.rc6.tar.gz.sig Some more fixes to bugs I noticed today while trying out some new things in production. Note especially the replicator-doveadm socket change, see http://wiki2.dovecot.org/Replication for how to configure it. This change allowed local replicator to notify the remote replicator

http://dovecot.org/releases/2.2/rc/dovecot-2.2.rc7.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.rc7.tar.gz.sig OK, still not quite v2.2.0, but now it's definitely very close. :) * checkpasword: AUTH_PASSWORD environment is no longer set. * Running dsync no longer triggers quota warnings. + dsync: Commit large transactions every 100 new messages, so if a large sync crashes it

http://dovecot.org/releases/2.2/rc/dovecot-2.2.rc7.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.rc7.tar.gz.sig OK, still not quite v2.2.0, but now it's definitely very close. :) * checkpasword: AUTH_PASSWORD environment is no longer set. * Running dsync no longer triggers quota warnings. + dsync: Commit large transactions every 100 new messages, so if a large sync crashes it

So, I'm still planning on getting v2.2.0 out Really Soon now. Unfortunately I've had to quickly develop some rather large features still at this stage. I was initially planning on leaving them for v2.3, but they were a requirement for one project and implementing them now to v2.2 was the least amount of trouble for me. (And yes, I'm aware I haven't replied to a lot of emails in

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

Two items I forgot to mention in my initial post: (A) I am running the sync command on the new v2.3 server. (B) To get sync to work, I had to add the following to the old v2.2 server: auth_socket_path = /var/run/dovecot/auth-master I think this relates to what I said in my initial post about AWS linux installing all of the sockets into a non-standard location. I say this because when I was

On 06/17/2015 06:07 PM, lejeczek wrote: > On 16/06/15 14:27, lejeczek wrote: >> On 16/06/15 14:16, lejeczek wrote: >>> On 16/06/15 13:14, B wrote: >>>> P, >>>> >>>> On Tue, Jun 16, 2015 at 01:07:52PM +0100, lejeczek wrote: >>>> >>>>> I've barely started reading on dsync and I wonder.. >>>>> would

> > With todays nightly: > > > > dsync(wsunpriv at iai.uni-bonn.de): Panic: file imapc-list.c: line 199 (imapc_list_get_vname): assertion failed: (strncmp(prefix, storage_name, prefix_len) == 0 && storage_name[prefix_len] == list->sep) > > Oh, and this would be good to solve too. What does it say with gdb: > > gdb dsync core > fr 5 > p prefix >