similar to: v2.0 / Master/config rewrite

I am currently running v1.1.20 and was wondering if there is any compelling reason to upgrade to v1.2 or v2.0? For example is there any security updates in v1.2 or v2.0 that aren't included in v1.1.20? The other major thing I would be interested in knowing is there any speed enhancements in the newer versions? I am using basic PAM Auth and Maildir mailboxes on a Linux box. Let me know

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

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

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

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:

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

Still broken, but I committed the current changes to http://hg.dovecot.org/dovecot-config-rewrite/ The idea is something like: - src/config/ contains a doveconf binary which can be used to dump the current configuration. It's the only binary that reads dovecot.conf directly. Currently the code is kind of ugly because I wanted it to be able to parse the existing v1.2 dovecot.conf which

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/1.1/rc/dovecot-1.1.rc1.tar.gz http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc1.tar.gz.sig Finally the first v1.1 release candidate. Please test so we can have a fully stable v1.1.0 release. v1.1.betas are already running in a few large installations, so I don't expect there to be many bugs left. There are no release critical bugs left and no known crash bugs.

http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc1.tar.gz http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc1.tar.gz.sig Finally the first v1.1 release candidate. Please test so we can have a fully stable v1.1.0 release. v1.1.betas are already running in a few large installations, so I don't expect there to be many bugs left. There are no release critical bugs left and no known crash bugs.

http://dovecot.org/releases/2.0/beta/dovecot-2.0.beta4.tar.gz http://dovecot.org/releases/2.0/beta/dovecot-2.0.beta4.tar.gz.sig I think this release is finally feature complete. There are still some bugs left to be fixed, but it's mainly in the dsync/mdbox area. v2.0.rc1 should hopefully be out in a couple of weeks. After that v2.0.0 will be released after no serious bugs have been found for

http://dovecot.org/releases/2.0/beta/dovecot-2.0.beta4.tar.gz http://dovecot.org/releases/2.0/beta/dovecot-2.0.beta4.tar.gz.sig I think this release is finally feature complete. There are still some bugs left to be fixed, but it's mainly in the dsync/mdbox area. v2.0.rc1 should hopefully be out in a couple of weeks. After that v2.0.0 will be released after no serious bugs have been found for

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

Hello Dovecot users, I have finally finished the first release of Pigeonhole for Dovecot v2.0. The most notable change from previous Dovecot v1.2 Sieve/ManageSieve releases is that all is now integrated in a single package and there is no need to patch Dovecot anymore to gain ManageSieve support. Changelog v0.2.0: * Merged Sieve and ManageSieve packages into a single Pigeonhole

Hello Dovecot users, I have finally finished the first release of Pigeonhole for Dovecot v2.0. The most notable change from previous Dovecot v1.2 Sieve/ManageSieve releases is that all is now integrated in a single package and there is no need to patch Dovecot anymore to gain ManageSieve support. Changelog v0.2.0: * Merged Sieve and ManageSieve packages into a single Pigeonhole

Hi Josh, I found id3v2 didn't work on v1.1.0. I checked source codes, macros- (in such cases as FLAC_HAVE_ID3LIB) ware moved to config.h. That is good. But the place to do include is the after of #ifdef FLAC_HAVE_ID3LIB. The result of configure script isn't reflected. And it doesn't always have id3lib with this. Move place of 'include "config.h"' to the top. I

http://dovecot.org/releases/1.1/dovecot-1.1.1.tar.gz http://dovecot.org/releases/1.1/dovecot-1.1.1.tar.gz.sig Hopefully this release lives a bit longer than v1.1.0. - Maildir: When migrating from v1.0 with old format dovecot-uidlist files, Dovecot may have appended lines to it using the new format and later broken with "UID larger than next_uid" error. -------------- next part

http://dovecot.org/releases/1.1/dovecot-1.1.1.tar.gz http://dovecot.org/releases/1.1/dovecot-1.1.1.tar.gz.sig Hopefully this release lives a bit longer than v1.1.0. - Maildir: When migrating from v1.0 with old format dovecot-uidlist files, Dovecot may have appended lines to it using the new format and later broken with "UID larger than next_uid" error. -------------- next part

http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc12.tar.gz http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc12.tar.gz.sig Sorry, one more RC because of the mbox+quota bug. v1.1.0 still planned for tomorrow. - mbox: Don't give "Can't find next message offset" warnings when plugin (e.g. quota) accesses the message being saved. - deliver: Settings inside protocol imap {}