[Dovecot] Updated v1.1 and summer plans
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:
- Index file optimizations: http://www.dovecot.org/list/dovecot/2007-May/022591.html
- Less indexing for POP3 users (both in pop3 and in deliver)
- Replace Squat FTS indexes with my new design
- Configurable mail_log plugin
- Limit number of connections for a user
- A combined LIST + STATUS command (or possibly NOTIFY extension? http://tools.ietf.org/html/draft-gulbrandsen-imap-notify-03)
- Fully supported shared mailboxes and IMAP ACL extension: http://www.dovecot.org/list/dovecot/2007-April/021624.html
- Remote (shared) mailboxes. Automatic proxying, but possibly also support for MAILBOX-REFERRALS extension if it's not much extra trouble (few clients support it, so probably not worth the trouble unless it can be done in a couple of hours)
- Remove unused keywords from mailboxes
- Some other small things
Upcoming v1.1/v1.2/v2.0 features (planned to be implemented at the end of the summer):
- virtual mailboxes: http://www.dovecot.org/list/dovecot/2007-May/022828.html
- dbox redesign: http://www.dovecot.org/list/dovecot/2007-May/022602.html
Implementing the above features will keep me busy for most of the summer, but there have also been requests for replication support (http://www.dovecot.org/list/dovecot/2007-May/022792.html). I'm interested in implementing it as well, but unfortunately it looks like I don't have time for it at least for the next 3 months or so.
There's already at least one company that's willing to pay for replication, but if you're also interested please let me know. Perhaps someone else could implement it instead (if you're interested, please let me know), or if not it'll just have to wait until I have time for it.
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:
Dear Timo,
How about managedsieve?
Regards, Steve
"Timo Sirainen" <tss@iki.fi> wrote in message news:1179753730.32181.1441.camel@hurina...
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.
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!"
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.
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
On Wed, 23 May 2007 08:59:29 -0500 "Brian G. Peterson" <brian@braverock.com> 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
On Mon, 2007-05-21 at 16:22 +0300, Timo Sirainen wrote:
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:
Nice, thanks for the updated pointer. Sounds like a really good idea, and with inotify it should be easy too. With dnotify you can quickly run into a situation where you don't have enough file descriptors though, maybe support it only when inotify is available. I'm definitely interested in this and would look into client support for e.g. evolution.
johannes
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!"
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.
participants (6)
-
Brian G. Peterson
-
Farkas Levente
-
Johannes Berg
-
M1
-
Marshal Newrock
-
Timo Sirainen