similar to: v1.1.20 vs v1.2 & v2.0

Hi Timo, I've just tried to convert my v1.2 configuration to a v2.0 configuration. Below a few obsolete warnings, among others "mail_executable has been replaced by service { executable }", was an interesting error: "doveconf: Error: duplicate listener: 198:" The broken parts of the converted configuration: # 2.0.beta4 (84ffb38839b9): /etc/dovecot/dovecot.conf # OS: Linux

v1.1.0 is finally getting closer, so it's time to start planning what happens after it. Below is a list of some of the larger features I'm planning on implementing. I'm not yet sure in which order, so I think it's time to ask again what features companies would be willing to pay for? Sponsoring Dovecot development gets you: - listed in Credits in www.dovecot.org - listed in

I forked the wiki to http://wiki1.dovecot.org/ is the old docs for v1.x http://wiki2.dovecot.org/ is the new docs for v2.0 For now wiki.dovecot.org points to wiki1, but once v2.0 is released I'll change it to point to wiki2. I symlinked the user directory, so users should stay synced between the wikis. The main reason for wiki2 is to be able to describe Dovecot v2.0's actual behavior

If anyone's interested, I updated my master/config rewrite to latest Dovecot v1.1 tree and added it to hg: http://hg.dovecot.org/dovecot-master-rewrite/ It probably doesn't work, but with the exception of plugins it compiles anyway. :) I'm thinking that maybe after v1.1.0 I could continue with the rewrite and create v2.0 after all instead of v1.2. Just look at how much cleaner

Hi Timo, I've just setup Dovecot v1.2.rc5 and switched the mailbox format of one account to dbox. Therefor I've created an empty directory, called dbox, with access mode 0700, like the user's home directory. After the IMAP login with Thunderbird some dboxes was created. All permissions were set fine (0700 / 0600), except the permissions for the files: *

On Sat, March 17, 2007 10:51 pm, Timo Sirainen <tss at iki.fi> said: > Oh, and as for when the rewrite is in CVS, I'm not really sure. I'm > still wondering if I should put it there soon and make the release after > v1.0 be v2.0, or if I should first stabilize the current new CVS HEAD > features (which shouldn't take too long), do a v1.2 release and only > then

Now supported by v2.0. Also as a patch to v1.2: http://dovecot.org/patches/1.2/zlib-compress.diff I'm not really sure if I should commit it to v1.2 code tree. The code contains ugly copy&pasted io_stream_copy() and v1.2 is supposed to be feature complete.. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature

http://dovecot.org/releases/1.1/dovecot-1.1.5.tar.gz http://dovecot.org/releases/1.1/dovecot-1.1.5.tar.gz.sig http://dovecot.org/releases/1.2/alpha/dovecot-1.2.alpha3.tar.gz http://dovecot.org/releases/1.2/alpha/dovecot-1.2.alpha3.tar.gz.sig A combined release announcement for a change. :) Largest changes since v1.1.4: * Dovecot prints an informational message about authentication problems

http://dovecot.org/releases/1.1/dovecot-1.1.5.tar.gz http://dovecot.org/releases/1.1/dovecot-1.1.5.tar.gz.sig http://dovecot.org/releases/1.2/alpha/dovecot-1.2.alpha3.tar.gz http://dovecot.org/releases/1.2/alpha/dovecot-1.2.alpha3.tar.gz.sig A combined release announcement for a change. :) Largest changes since v1.1.4: * Dovecot prints an informational message about authentication problems

http://dovecot.org/releases/1.1/dovecot-1.1.14.tar.gz http://dovecot.org/releases/1.1/dovecot-1.1.14.tar.gz.sig http://dovecot.org/releases/1.2/rc/dovecot-1.2.rc3.tar.gz http://dovecot.org/releases/1.2/rc/dovecot-1.2.rc3.tar.gz.sig Fixed lots of bugs in v1.2 related to shared mailboxes and virtual mailboxes. Keep on testing and sending bug reports and hopefully we'll get v1.2.0 release out

http://dovecot.org/releases/1.1/dovecot-1.1.14.tar.gz http://dovecot.org/releases/1.1/dovecot-1.1.14.tar.gz.sig http://dovecot.org/releases/1.2/rc/dovecot-1.2.rc3.tar.gz http://dovecot.org/releases/1.2/rc/dovecot-1.2.rc3.tar.gz.sig Fixed lots of bugs in v1.2 related to shared mailboxes and virtual mailboxes. Keep on testing and sending bug reports and hopefully we'll get v1.2.0 release out

http://hg.dovecot.org/dovecot-2.0/ I just did the initial commit for master process rewrite, which marks the beginning of Dovecot v2.0. Several things are still missing/broken, but at least I was just able to successfully log in using imap :) I left v1.3 hg tree there for now, but once v2.0 tree is fully usable I'll just delete the v1.3 tree. Note the new dovecot-master-example.conf, which

http://dovecot.org/releases/2.0/alpha/dovecot-2.0.alpha1.tar.gz http://dovecot.org/releases/2.0/alpha/dovecot-2.0.alpha1.tar.gz.sig So here's the first alpha version of Dovecot v2.0. There are still a couple of things left to do, but in general it should work for most people. I started using it for my own mails a few days ago and it seems to work without errors. Largest changes since v1.2:

http://dovecot.org/releases/2.0/alpha/dovecot-2.0.alpha1.tar.gz http://dovecot.org/releases/2.0/alpha/dovecot-2.0.alpha1.tar.gz.sig So here's the first alpha version of Dovecot v2.0. There are still a couple of things left to do, but in general it should work for most people. I started using it for my own mails a few days ago and it seems to work without errors. Largest changes since v1.2:

I merged all the new features and latest v1.1 changes under one tree: http://hg.dovecot.org/dovecot-1.2/ The changeset order is kind of weird though. The timestamps jump all around. Wonder if there's a way to reorder them so that it looks more sane.. The status of the new features: 1. CONDSTORE extension is probably the largest change. It adds new "modification sequences" for

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

Hello, i have a problem with the managesieve plugin and a virtual namespace in v2.0. The managesieve plugin complains about an unknown storage driver virtual when i try to log intot the managesieve. I don't know if this is quite a recent problem or if it exists for a while, as i configured the virtual namspace from scratch. (The virtual namespace itself is working.) Jun 28 13:55:54

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

http://dovecot.org/releases/1.1/dovecot-1.1.12.tar.gz http://dovecot.org/releases/1.1/dovecot-1.1.12.tar.gz.sig http://dovecot.org/releases/1.2/beta/dovecot-1.2.beta2.tar.gz http://dovecot.org/releases/1.2/beta/dovecot-1.2.beta2.tar.gz.sig I thought I'd do a double-release since it's Friday the 13th. v1.2.0 is getting closer, mainly some ACL fixes left. Changes in v1.2.beta2 since