Re: [Dovecot] v1.1.rc1 released
On Tue, 4 Mar 2008, Timo Sirainen wrote: On Feb 22, 2008, at 9:42 AM, Gerhard Wiesinger wrote: Hello Timo! Looks like that mbox index handling still doesn't work with deliver: 1.) 1s mail delivered: Only dovecot.index.log is generated. This is correct. dovecot.index doesn't need to be created/updated always, and dovecot.index.cache isn't created because there's nothing that's known wanted to be cached. Hmmm. But shouldn't this be a feature of 1.1 that deliver updates indexes at deliver time? (maybe you can choose the typical indexes the clients use). Updating dovecot.index.log is enough. v1.0 unneededly wastes disk I/O writing to dovecot.index way too often. I don't think this is wasted disk I/O updating indexes as soon as possible. When the mailbox (mbox) is read afterwards on large mboxes there is much more waste in reading large files. e.g. When deliver would write e.g. 3 mails with 40 MB: 1.) with indexes write large mailbox update small index reopen: only read small index 2.) without indexes write large mailbox reopen: read large mailbox update small index So case 1 with indexes is IHMO in total more efficient. 1. deliver the first mail 2. open the mailbox 3. deliver lots of large mails 4. open the mailbox again It should be fast. (and I just tested - it is) Yes, that's exactly the testcase I use. But here it is slow (opening is always done with doevecot 1.0.latest/alpine 1.00 and deliver is done with 1.1.rc1). I use large files to see a time I see on the first look on opening. Check with v1.1's idxview what the index file contains after steps 2, 3 and 4. After step 2 it should contain for the first message all the cached fields that client needs. Between 3 and 4 steps there should be no changes, and the cache fields should be exactly the same with the same decision rules as with step 2. I will check that. Ciao, Gerhard -- http://www.wiesinger.com/
Re: [Dovecot] v1.1.rc1 released
On Mar 7, 2008, at 8:56 AM, Gerhard Wiesinger wrote: Updating dovecot.index.log is enough. v1.0 unneededly wastes disk I/ O writing to dovecot.index way too often. I don't think this is wasted disk I/O updating indexes as soon as possible. When the mailbox (mbox) is read afterwards on large mboxes there is much more waste in reading large files. You misunderstood what I meant. dovecot.index isn't updated/created always, because dovecot.index.log already contains all the necessary data to build dovecot.index file (which is what Dovecot internally does). e.g. When deliver would write e.g. 3 mails with 40 MB: 1.) with indexes write large mailbox update small index reopen: only read small index It should still work like this. PGP.sig Description: This is a digitally signed message part
Re: [Dovecot] v1.1.rc1 released
On Feb 22, 2008, at 9:42 AM, Gerhard Wiesinger wrote: Hello Timo! Looks like that mbox index handling still doesn't work with deliver: 1.) 1s mail delivered: Only dovecot.index.log is generated. This is correct. dovecot.index doesn't need to be created/updated always, and dovecot.index.cache isn't created because there's nothing that's known wanted to be cached. Hmmm. But shouldn't this be a feature of 1.1 that deliver updates indexes at deliver time? (maybe you can choose the typical indexes the clients use). Updating dovecot.index.log is enough. v1.0 unneededly wastes disk I/O writing to dovecot.index way too often. 1. deliver the first mail 2. open the mailbox 3. deliver lots of large mails 4. open the mailbox again It should be fast. (and I just tested - it is) Yes, that's exactly the testcase I use. But here it is slow (opening is always done with doevecot 1.0.latest/alpine 1.00 and deliver is done with 1.1.rc1). I use large files to see a time I see on the first look on opening. Check with v1.1's idxview what the index file contains after steps 2, 3 and 4. After step 2 it should contain for the first message all the cached fields that client needs. Between 3 and 4 steps there should be no changes, and the cache fields should be exactly the same with the same decision rules as with step 2. PGP.sig Description: This is a digitally signed message part
Re: [Dovecot] v1.1.rc1 released
Timo Sirainen wrote: 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. So far it's been smooth ride for me, upgraded from 1.0.10 last night. Quick specs of my setup * Solaris 10 x86 * Compiled with Sun Studio 12 * Maildir storage on ZFS * Dovecot indexes on compressed ZFS * MySQL 5 as user data backend * Postfix with Dovecot SASL and Dovecot Deliver * Plugins in use: quota, imap quota, fts, fts squat * Users ~30 * Clients in use: Thunderbird, RoundCube Webmail, Nokia smartphones Tomi
Re: [Dovecot] v1.1.rc1 released
* Timo Sirainen [EMAIL PROTECTED] [2008-02-22 14:35]: On Fri, 2008-02-22 at 08:32 -0500, Bruce Bodger wrote: On Feb 21, 2008, at 4:22 PM, Timo Sirainen wrote: http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc1.tar.gz Timo, You probably want to announce the availability of Sieve plugin v1.1.4 as well. I thought that people will figure out automatically that they need a newer version since older ones won't compile. :) Actually 1.1.3 got broken already in beta16 (or 15?). Yeah :P I just committed the Gentoo ebuild for 1.1.rc1 with sieve and managesieve support (both since 1.1.beta15): http://packages.gentoo.org/package/net-mail/dovecot Have fun! -- Regards, Wolfram Schlich [EMAIL PROTECTED] Gentoo Linux * http://dev.gentoo.org/~wschlich/
Re: [Dovecot] v1.1.rc1 released
On Sat, 23 Feb 2008, Wolfram Schlich wrote: I just committed the Gentoo ebuild for 1.1.rc1 with sieve and managesieve support (both since 1.1.beta15): http://packages.gentoo.org/package/net-mail/dovecot I've also made available unofficial Debian packages. Note that they don't have Sieve support. I'd suggest compiling them yourself. I compiled them against Debian Stable amd64 and they work well there; you can just apt-get install dovecot after adding my repositories if you want to use my binaries. Here's how to do use the source packages: 1. Edit your sources.list to include my repository Add these lines: deb http://www.asheesh.org/ubuntu/ sid main deb-src http://www.asheesh.org/ubuntu/ sid main 2. Install apt-src so you can build the packages yourself $ sudo aptitude install apt-src 3. Use apt-src to build (note: it doesn't install by default) the new Dovecot packages $ apt-src -b install dovecot 4. Install the resulting .deb files: $ sudo dpkg -i *.deb Have fun! Yes, have fun! (-: -- Asheesh. -- He asked me if I knew what time it was -- I said yes, but not right now. -- Steven Wright
Re: [Dovecot] v1.1.rc1 released
On Feb 21, 2008, at 4:22 PM, Timo Sirainen wrote: http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc1.tar.gz Timo, You probably want to announce the availability of Sieve plugin v1.1.4 as well. Here, running OS X 10.4.11, it is required after the upgrade to 1.1.rc1. Without upgrading to dovecot-sieve-1.1.4 I get these errors during the 'make': sieve-cmu.Tpo -c sieve-cmu.c -fno-common -DPIC -o .libs/sieve-cmu.o sieve-cmu.c: In function 'parts_add_missing': sieve-cmu.c:323: error: too few arguments to function 'message_parser_deinit' make[3]: *** [sieve-cmu.lo] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 B. Bodger New York, NY
Re: [Dovecot] v1.1.rc1 released
On Fri, 2008-02-22 at 08:32 -0500, Bruce Bodger wrote: On Feb 21, 2008, at 4:22 PM, Timo Sirainen wrote: http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc1.tar.gz Timo, You probably want to announce the availability of Sieve plugin v1.1.4 as well. I thought that people will figure out automatically that they need a newer version since older ones won't compile. :) Actually 1.1.3 got broken already in beta16 (or 15?). signature.asc Description: This is a digitally signed message part
