Re: [Dovecot] Updated v1.1 and summer plans
On 12/2/2007, Timo Sirainen ([EMAIL PROTECTED]) wrote: On Sat, 2007-12-01 at 18:56 -0500, Charles Marcus wrote: I don't see any mention of support for SiS (single-instance-storage) as discussed previously on the list, even for upcoming 1.2/2.0 Did this fall through a crack? Or did you decide it was going to be too difficult for the time being? dbox-file.h contains: /* Pointer to external message data. Format is: 1*(start offset byte count ref) */ DBOX_METADATA_EXT_REF= 'P', That's about all there exists of that feature :) I haven't given up on implementing that, but for now there have been more important things. Fair enough... but since this one is near and dear to my heart ;) Do you have any idea as to a time frame for when you might be able to get to it? Are you thinking post v2.0? Even 2.1 or 3.0? I know its a hard question to answer, so if you just have no idea, thats ok too... Thanks again - -- Best regards, Charles
Re: [Dovecot] Updated v1.1 and summer plans
On 12/2/2007, Adam McDougall ([EMAIL PROTECTED]) wrote: Another option to consider is server side deduplication such as the ASIS block-level deduplication offered by NetApp (requires nearstore license). Our site will be migrating to a new netapp cluster that supports dedupe and I will probably use it for mail. Although I doubt it does anything for tape backups, I assume those will be full size. Dovecot is cheaper too :) Well, yeah, that'd be nice, but NetApps are expensive, and my boss wouldn't even consider it... ;) this is a pretty small shop. -- Best regards, Charles
Re: [Dovecot] Updated v1.1 and summer plans
On Sun, 2007-12-02 at 10:02 -0500, Charles Marcus wrote: On 12/2/2007, Timo Sirainen ([EMAIL PROTECTED]) wrote: On Sat, 2007-12-01 at 18:56 -0500, Charles Marcus wrote: I don't see any mention of support for SiS (single-instance-storage) as discussed previously on the list, even for upcoming 1.2/2.0 Did this fall through a crack? Or did you decide it was going to be too difficult for the time being? dbox-file.h contains: /* Pointer to external message data. Format is: 1*(start offset byte count ref) */ DBOX_METADATA_EXT_REF= 'P', That's about all there exists of that feature :) I haven't given up on implementing that, but for now there have been more important things. Fair enough... but since this one is near and dear to my heart ;) Do you have any idea as to a time frame for when you might be able to get to it? Are you thinking post v2.0? Even 2.1 or 3.0? Right now I just want to get v1.1 finished. The main problem with it is that apparently in some installations it's slower than v1.0 and I haven't yet figured out why. And I want Squat rewrite to be included in it too (almost finished! just committed it to hg). After v1.1 I'm not sure. I'm more interested in implementing other features first (like v2.0's config rewrite, replication, etc.), but once I'm beginning to run out of money I'll start doing pretty much anything people pay me to do ;) signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Updated v1.1 and summer plans
On Sat, 2007-12-01 at 18:56 -0500, Charles Marcus wrote: I don't see any mention of support for SiS (single-instance-storage) as discussed previously on the list, even for upcoming 1.2/2.0 Did this fall through a crack? Or did you decide it was going to be too difficult for the time being? dbox-file.h contains: /* Pointer to external message data. Format is: 1*(start offset byte count ref) */ DBOX_METADATA_EXT_REF = 'P', That's about all there exists of that feature :) I haven't given up on implementing that, but for now there have been more important things. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Updated v1.1 and summer plans
Timo Sirainen wrote: On Tue, 2007-05-22 at 00:52 +0800, M1 wrote: Dear Timo, How about managedsieve? I think it'll have to wait for v2.0. Especially because I want it to be distributed in dovecot-sieve package, not in the main dovecot package. This just isn't possible without the larger changes that v2.0 brings. but it'd be a real need for everyone who use lda since we can't use procmail any longer and there is no other option:-( -- Levente Si vis pacem para bellum!
Re: [Dovecot] Updated v1.1 and summer plans
On Wed, 2007-05-23 at 13:43 +0200, Farkas Levente wrote: Timo Sirainen wrote: On Tue, 2007-05-22 at 00:52 +0800, M1 wrote: Dear Timo, How about managedsieve? I think it'll have to wait for v2.0. Especially because I want it to be distributed in dovecot-sieve package, not in the main dovecot package. This just isn't possible without the larger changes that v2.0 brings. but it'd be a real need for everyone who use lda since we can't use procmail any longer and there is no other option:-( Oh, procmail had manageprocmail too? There's no reason why procmail can't be used, and there's no reason why one of the two managesieve implementations can't be used. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Updated v1.1 and summer plans
Timo Sirainen wrote: Webmail.us will be sponsoring my Dovecot development for this summer. Other companies are also welcome to participate in the costs. Participation gets you: - listed in Credits in www.dovecot.org - listed in AUTHORS file - you can tell me how you want to use the feature and I'll make sure that it supports it (within reasonable limits) For already implemented v1.1 features, see http://www.dovecot.org/list/dovecot/2007-April/021974.html Some of those features require some more testing (new SORT and THREAD code especially) and a bit of fixes to mailbox list indexes. Otherwise I think it's working pretty well already, I've been using it for a long time for my own mails. Upcoming v1.1 features, more or less implemented in this order: what's the plan for the 1.0 series? it'll be 1.0.x release soon and ofter or ...? yours. -- Levente Si vis pacem para bellum!
Re: [Dovecot] Updated v1.1 and summer plans
On Tue, 2007-05-22 at 16:48 +0200, Farkas Levente wrote: what's the plan for the 1.0 series? it'll be 1.0.x release soon and ofter or ...? v1.0.1 will be released soon. I'm mostly just waiting to see if one user's problems go away with http://hg.dovecot.org/dovecot-1.0/rev/4e4572280ef1 If I don't hear back in a few days I guess I'll do the release. Well, now that you mentioned it I built also 1.0.1rc tarball for people to test: http://dovecot.org/tmp/dovecot-1.0.1rc.tar.gz It has only small changes so I don't think it can break anything. Other 1.0.x releases will come then if bugs are found. Probably even after v1.1.0. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Updated v1.1 and summer plans
On Tue, 2007-05-22 at 00:52 +0800, M1 wrote: Dear Timo, How about managedsieve? I think it'll have to wait for v2.0. Especially because I want it to be distributed in dovecot-sieve package, not in the main dovecot package. This just isn't possible without the larger changes that v2.0 brings. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Updated v1.1 and summer plans
Timo Sirainen wrote: On Tue, 2007-05-22 at 00:52 +0800, M1 wrote: Dear Timo, How about managedsieve? I think it'll have to wait for v2.0. Especially because I want it to be distributed in dovecot-sieve package, not in the main dovecot package. This just isn't possible without the larger changes that v2.0 brings. Please do put a manageSIEVE interface formally on the roadmap. (I'd vote for v1.1, but I understand the technical issues that may push it to 2.0). SIEVE really isn't useful without a manageSIEVE interface or a shell. It would be very nice to have it in the official dovecot packages, rather than as an add-on developed by another group. The efforts of others who have added manageSIEVE support as a bolt-on are appreciated, but an official version would be preferable. Regards, - Brian
Re: [Dovecot] Updated v1.1 and summer plans
On Wed, 23 May 2007 08:59:29 -0500 Brian G. Peterson [EMAIL PROTECTED] wrote: Timo Sirainen wrote: On Tue, 2007-05-22 at 00:52 +0800, M1 wrote: Dear Timo, How about managedsieve? I think it'll have to wait for v2.0. Especially because I want it to be distributed in dovecot-sieve package, not in the main dovecot package. This just isn't possible without the larger changes that v2.0 brings. Please do put a manageSIEVE interface formally on the roadmap. (I'd vote for v1.1, but I understand the technical issues that may push it to 2.0). SIEVE really isn't useful without a manageSIEVE interface or a shell. I would like to request that this also be capable of being a proxy, similar to the pop/imap proxy. -- Marshal Newrock Ideal Solution, LLC - http://www.idealso.com
Re: [Dovecot] Updated v1.1 and summer plans
Dear Timo, How about managedsieve? Regards, Steve Timo Sirainen [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED]
Re: [Dovecot] Updated v1.1 and summer plans
On Mon, 2007-05-21 at 16:02 +0300, Timo Sirainen wrote: - A combined LIST + STATUS command (or possibly NOTIFY extension? http://tools.ietf.org/html/draft-gulbrandsen-imap-notify-03) If anyone considered reading that, read a newer draft instead: http://tools.ietf.org/html/draft-gulbrandsen-imap-notify-05 signature.asc Description: This is a digitally signed message part
