[Dovecot] v1.1.alpha1 released
http://dovecot.org/releases/1.1/alpha/dovecot-1.1.alpha1.tar.gz http://dovecot.org/releases/1.1/alpha/dovecot-1.1.alpha1.tar.gz.sig
This is the first alpha release of Dovecot v1.1. I hope that it stabilizes into final release within a few months. There are a lot of new features since v1.0. The most important ones are listed at the end of this post.
This is the only v1.1.alpha announcement I send to dovecot-news list (or to www.dovecot.org news). The next one probably will be v1.1.rc1.
I've been stress testing the code a lot and I've also been using it myself for almost a year, so I think this release should actually be quite stable and usable. But since I haven't tested everything, there might be some crashes and misbehaving commands.
So this release should now have all the major features that I intend to add to v1.1 (except for dbox rewrite, see below). Some smaller features will still be added. The rest of the major features in my previous v1.1 list will go to v1.2.
While v1.1 is getting stabilized I'm beginning to rewrite dbox code. Its code is isolated from the rest of Dovecot, so it can't destabilize anything else. Hopefully it will be ready before v1.1 release, although maybe still marked as experimental.
Some of the features might not be considered quite ready yet:
Mailbox list indexes improve STATUS performance a lot (maybe 7x) when mailboxes haven't changed. Handling updates however is a lot slower than I'd want (2x with one client, more with multiple), so you may want to disable them with mailbox_list_index_disable=yes until the update performance gets better.
THREAD code is completely rewritten with support for incremental updates and index files. I tested it last year and it seemed OK, but I didn't dare try it now so I wouldn't have to delay this alpha if it was broken :) I'll do some more testing soon, but for now be careful with using v1.1 with webmails.
SORT code also uses indexes now, but it's a lot simpler so it probably works.
Squat indexes work and I'm using them myself, but they'll be rewritten for v1.2 with a new faster format.
Although Dovecot now flushes NFS attribute/data caches when needed, I'm not sure if it's done in all the necessary places.
I don't remember if I've tested expire plugin at all.
So, the largest changes I've added to NEWS file (which BTW won't contain changes between alphas/betas/rcs, those will be only in my mailing list posts):
* After Dovecot v1.1 has modified index or dovecot-uidlist files,
they can't be opened anymore with Dovecot versions earlier than
v1.0.2.
* Empty passwords in passdb doesn't allow user to log in with any
password anymore. To do that you'll also need to set nopassword
extra field.
+ IMAP: Added support for UIDPLUS and LIST-EXTENDED extensions.
+ IMAP SORT: Sort keys are indexed, which makes SORT commands faster.
+ IMAP THREAD: Threads are indexed into a dovecot.index.thread file.
It can usually be updated incrementally, so this makes THREAD fast.
+ Added Dovecot-specific X-REFERENCES2 threading algorithm.
It's similar to REFERENCES, but it doesn't do base subject merging
and it sorts the threads by their newest message.
+ When saving messages, update cache file immediately with the data
that we expect client to fetch later. Maildir-only currently.
+ NFS attribute and data caches are are flushed whenever needed.
See mail_nfs_storage and mail_nfs_index settings.
+ Mailbox list indexes. Mailbox metadata is stored there, so STATUS
commands can return synchronized mailboxes' metadata simply by
reading a single mailbox list index file. Currently works only with
Maildir++ layout.
+ Out of order command execution (SEARCH, FETCH, LIST), nonstandard
command cancellation (X-CANCEL <tag>)
+ Expire plugin can be used to keep track of oldest messages in
specific mailboxes. A nightly run can then quickly expunge old
messages from the mailboxes that have them. The tracking is done
using lib-dict, so you can use either Berkeley DB or SQL database.
+ Namespaces are supported everywhere now.
+ Full text search indexing support with Lucene and Squat backends.
+ OTP and S/KEY authentication mechanisms (by Andrey Panin).
+ mbox and Maildir works with both Maildir++ and FS layouts. You can
change these by appending :LAYOUT=maildir++ or :LAYOUT=fs to
mail_location.
+ LDAP: Support templates in pass_attrs and user_attrs
+ Support for listening in multiple IPs/ports.
+ Quota plugin rewrite: Support for multiple quota roots, warnings,
allow giving storage size in bytes or kilo/mega/giga/terabytes,
per-mailbox quota rules.Hello Timo!
Is the deliver/index update code also included for mbox mailboxes?
Ciao, Gerhard
On Thu, 19 Jul 2007, Timo Sirainen wrote:
http://dovecot.org/releases/1.1/alpha/dovecot-1.1.alpha1.tar.gz http://dovecot.org/releases/1.1/alpha/dovecot-1.1.alpha1.tar.gz.sig
This is the first alpha release of Dovecot v1.1. I hope that it stabilizes into final release within a few months. There are a lot of new features since v1.0. The most important ones are listed at the end of this post.
This is the only v1.1.alpha announcement I send to dovecot-news list (or to www.dovecot.org news). The next one probably will be v1.1.rc1.
I've been stress testing the code a lot and I've also been using it myself for almost a year, so I think this release should actually be quite stable and usable. But since I haven't tested everything, there might be some crashes and misbehaving commands.
So this release should now have all the major features that I intend to add to v1.1 (except for dbox rewrite, see below). Some smaller features will still be added. The rest of the major features in my previous v1.1 list will go to v1.2.
While v1.1 is getting stabilized I'm beginning to rewrite dbox code. Its code is isolated from the rest of Dovecot, so it can't destabilize anything else. Hopefully it will be ready before v1.1 release, although maybe still marked as experimental.
Some of the features might not be considered quite ready yet:
Mailbox list indexes improve STATUS performance a lot (maybe 7x) when mailboxes haven't changed. Handling updates however is a lot slower than I'd want (2x with one client, more with multiple), so you may want to disable them with mailbox_list_index_disable=yes until the update performance gets better.
THREAD code is completely rewritten with support for incremental updates and index files. I tested it last year and it seemed OK, but I didn't dare try it now so I wouldn't have to delay this alpha if it was broken :) I'll do some more testing soon, but for now be careful with using v1.1 with webmails.
SORT code also uses indexes now, but it's a lot simpler so it probably works.
Squat indexes work and I'm using them myself, but they'll be rewritten for v1.2 with a new faster format.
Although Dovecot now flushes NFS attribute/data caches when needed, I'm not sure if it's done in all the necessary places.
I don't remember if I've tested expire plugin at all.
So, the largest changes I've added to NEWS file (which BTW won't contain changes between alphas/betas/rcs, those will be only in my mailing list posts):
- After Dovecot v1.1 has modified index or dovecot-uidlist files, they can't be opened anymore with Dovecot versions earlier than v1.0.2.
- Empty passwords in passdb doesn't allow user to log in with any password anymore. To do that you'll also need to set nopassword extra field.
- IMAP: Added support for UIDPLUS and LIST-EXTENDED extensions.
- IMAP SORT: Sort keys are indexed, which makes SORT commands faster.
- IMAP THREAD: Threads are indexed into a dovecot.index.thread file. It can usually be updated incrementally, so this makes THREAD fast.
- Added Dovecot-specific X-REFERENCES2 threading algorithm. It's similar to REFERENCES, but it doesn't do base subject merging and it sorts the threads by their newest message.
- When saving messages, update cache file immediately with the data that we expect client to fetch later. Maildir-only currently.
- NFS attribute and data caches are are flushed whenever needed. See mail_nfs_storage and mail_nfs_index settings.
- Mailbox list indexes. Mailbox metadata is stored there, so STATUS commands can return synchronized mailboxes' metadata simply by reading a single mailbox list index file. Currently works only with Maildir++ layout.
- Out of order command execution (SEARCH, FETCH, LIST), nonstandard command cancellation (X-CANCEL <tag>)
- Expire plugin can be used to keep track of oldest messages in specific mailboxes. A nightly run can then quickly expunge old messages from the mailboxes that have them. The tracking is done using lib-dict, so you can use either Berkeley DB or SQL database.
- Namespaces are supported everywhere now.
- Full text search indexing support with Lucene and Squat backends.
- OTP and S/KEY authentication mechanisms (by Andrey Panin).
- mbox and Maildir works with both Maildir++ and FS layouts. You can change these by appending :LAYOUT=maildir++ or :LAYOUT=fs to mail_location.
- LDAP: Support templates in pass_attrs and user_attrs
- Support for listening in multiple IPs/ports.
- Quota plugin rewrite: Support for multiple quota roots, warnings, allow giving storage size in bytes or kilo/mega/giga/terabytes, per-mailbox quota rules.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Timo Sirainen schrieb:
http://dovecot.org/releases/1.1/alpha/dovecot-1.1.alpha1.tar.gz http://dovecot.org/releases/1.1/alpha/dovecot-1.1.alpha1.tar.gz.sig
This is the first alpha release of Dovecot v1.1. I hope that it stabilizes into final release within a few months. There are a lot of new features since v1.0. The most important ones are listed at the end of this post.
This is the only v1.1.alpha announcement I send to dovecot-news list (or to www.dovecot.org news). The next one probably will be v1.1.rc1.
I've been stress testing the code a lot and I've also been using it myself for almost a year, so I think this release should actually be quite stable and usable. But since I haven't tested everything, there might be some crashes and misbehaving commands.
So this release should now have all the major features that I intend to add to v1.1 (except for dbox rewrite, see below). Some smaller features will still be added. The rest of the major features in my previous v1.1 list will go to v1.2.
While v1.1 is getting stabilized I'm beginning to rewrite dbox code. Its code is isolated from the rest of Dovecot, so it can't destabilize anything else. Hopefully it will be ready before v1.1 release, although maybe still marked as experimental.
Some of the features might not be considered quite ready yet:
Mailbox list indexes improve STATUS performance a lot (maybe 7x) when mailboxes haven't changed. Handling updates however is a lot slower than I'd want (2x with one client, more with multiple), so you may want to disable them with mailbox_list_index_disable=yes until the update performance gets better.
THREAD code is completely rewritten with support for incremental updates and index files. I tested it last year and it seemed OK, but I didn't dare try it now so I wouldn't have to delay this alpha if it was broken :) I'll do some more testing soon, but for now be careful with using v1.1 with webmails.
SORT code also uses indexes now, but it's a lot simpler so it probably works.
Squat indexes work and I'm using them myself, but they'll be rewritten for v1.2 with a new faster format.
Although Dovecot now flushes NFS attribute/data caches when needed, I'm not sure if it's done in all the necessary places.
I don't remember if I've tested expire plugin at all.
So, the largest changes I've added to NEWS file (which BTW won't contain changes between alphas/betas/rcs, those will be only in my mailing list posts):
- After Dovecot v1.1 has modified index or dovecot-uidlist files, they can't be opened anymore with Dovecot versions earlier than v1.0.2.
- Empty passwords in passdb doesn't allow user to log in with any password anymore. To do that you'll also need to set nopassword extra field.
- IMAP: Added support for UIDPLUS and LIST-EXTENDED extensions.
- IMAP SORT: Sort keys are indexed, which makes SORT commands faster.
- IMAP THREAD: Threads are indexed into a dovecot.index.thread file. It can usually be updated incrementally, so this makes THREAD fast.
- Added Dovecot-specific X-REFERENCES2 threading algorithm. It's similar to REFERENCES, but it doesn't do base subject merging and it sorts the threads by their newest message.
- When saving messages, update cache file immediately with the data that we expect client to fetch later. Maildir-only currently.
- NFS attribute and data caches are are flushed whenever needed. See mail_nfs_storage and mail_nfs_index settings.
- Mailbox list indexes. Mailbox metadata is stored there, so STATUS commands can return synchronized mailboxes' metadata simply by reading a single mailbox list index file. Currently works only with Maildir++ layout.
- Out of order command execution (SEARCH, FETCH, LIST), nonstandard command cancellation (X-CANCEL <tag>)
- Expire plugin can be used to keep track of oldest messages in specific mailboxes. A nightly run can then quickly expunge old messages from the mailboxes that have them. The tracking is done using lib-dict, so you can use either Berkeley DB or SQL database.
- Namespaces are supported everywhere now.
- Full text search indexing support with Lucene and Squat backends.
- OTP and S/KEY authentication mechanisms (by Andrey Panin).
- mbox and Maildir works with both Maildir++ and FS layouts. You can change these by appending :LAYOUT=maildir++ or :LAYOUT=fs to mail_location.
- LDAP: Support templates in pass_attrs and user_attrs
- Support for listening in multiple IPs/ports.
- Quota plugin rewrite: Support for multiple quota roots, warnings, allow giving storage size in bytes or kilo/mega/giga/terabytes, per-mailbox quota rules.
Hi Timo, wasnt full imap acl planed for the 1.1 release, i dont see it here .....should i take new glasses*gg??
Mit freundlichen Gruessen Best Regards
Robert Schetterer
https://www.schetterer.org Germany -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org
iD8DBQFGnwzIfGH2AvR16oERAtLOAJ9IDPcEXxnBUz0Yob3q+PdcqvXkNgCdFQfh Eohn5wduyfIBRMksJOAirME= =N/EL -----END PGP SIGNATURE-----
On Thu, 2007-07-19 at 09:03 +0200, Robert Schetterer wrote:
Hi Timo, wasnt full imap acl planed for the 1.1 release, i dont see it here .....should i take new glasses*gg??
It was, but the plans changed a bit because some people want to have dbox rewrite in production in a couple of months. :)
So the plan is now to get a stable v1.1 out soon, do the dbox rewrite and after that continue with v1.2 which will have ACLs, virtual mailboxes, etc.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Timo Sirainen schrieb:
On Thu, 2007-07-19 at 09:03 +0200, Robert Schetterer wrote:
Hi Timo, wasnt full imap acl planed for the 1.1 release, i dont see it here .....should i take new glasses*gg??
It was, but the plans changed a bit because some people want to have dbox rewrite in production in a couple of months. :)
So the plan is now to get a stable v1.1 out soon, do the dbox rewrite and after that continue with v1.2 which will have ACLs, virtual mailboxes, etc.
Ok, i understand , sounds great
Mit freundlichen Gruessen Best Regards
Robert Schetterer
https://www.schetterer.org Germany -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org
iD8DBQFGnyW3fGH2AvR16oERAnSdAJ4qraPa8iFrXbChCCLkkGKvkG4oTACfVgLn z1XqmYzpc8mboAjYbk+yZP8= =SVAx -----END PGP SIGNATURE-----
On 7/19/2007, Timo Sirainen (tss@iki.fi) wrote:
So the plan is now to get a stable v1.1 out soon, do the dbox rewrite and after that continue with v1.2 which will have ACLs, virtual mailboxes, etc.
Where is single-instance-storage now on the roadmap? Is that a 2.0+ feature? Or maybe 1.2 or 1.3?
Just curious...
Dovecot just keep getting better and better... thanks!
--
Best regards,
Charles
On 19.7.2007, at 17.12, Charles Marcus wrote:
On 7/19/2007, Timo Sirainen (tss@iki.fi) wrote:
So the plan is now to get a stable v1.1 out soon, do the dbox rewrite and after that continue with v1.2 which will have ACLs, virtual mailboxes, etc.
Where is single-instance-storage now on the roadmap? Is that a 2.0+
feature? Or maybe 1.2 or 1.3?
It's a dbox feature, so probably v1.2, maybe even v1.1.
Where is single-instance-storage now on the roadmap? Is that a 2.0+ feature? Or maybe 1.2 or 1.3?
It's a dbox feature, so probably v1.2, maybe even v1.1.
Wheee! Cool... but two follow-ups if you don't mind...
Is this going to initially be just for attachments? Or for the entire message (not a big deal if it is only attachments, as it is attachments I'm mostly concerned about)?
and
Will conversion of an existing mail store take place automatically (as users are converted to dbox), or will there be a migration tool of some kind?
Thanks again for all you do!
--
Best regards,
Charles
On 19.7.2007, at 23.53, Charles Marcus wrote:
Where is single-instance-storage now on the roadmap? Is that a 2.0
- feature? Or maybe 1.2 or 1.3?
It's a dbox feature, so probably v1.2, maybe even v1.1.
Wheee! Cool... but two follow-ups if you don't mind...
Is this going to initially be just for attachments? Or for the
entire message (not a big deal if it is only attachments, as it is
attachments I'm mostly concerned about)?
I think I'll make the dbox format itself support both, but at least
initially it's done only for attachments.
Will conversion of an existing mail store take place automatically
(as users are converted to dbox), or will there be a migration tool
of some kind?
Convert plugin can be used to do that. I was thinking about making
maildir -> dbox conversion superfast by allowing the maildir files be
used directly as dbox files. Only when some dbox metadata needs to be
written the file will have to be rewritten into dbox format.
On 7/19/2007, Timo Sirainen (tss@iki.fi) wrote:
Is this going to initially be just for attachments? Or for the entire message (not a big deal if it is only attachments, as it is attachments I'm mostly concerned about)?
I think I'll make the dbox format itself support both, but at least initially it's done only for attachments.
By the way... it just occurred to me...
We are talking about Single Instance Storage across the entire namespace, not just on a per dbox file, right?
Will conversion of an existing mail store take place automatically (as users are converted to dbox), or will there be a migration tool of some kind?
Convert plugin can be used to do that. I was thinking about making maildir -> dbox conversion superfast by allowing the maildir files be used directly as dbox files. Only when some dbox metadata needs to be written the file will have to be rewritten into dbox format.
Interesting - so they would auto-self-convert only when necessary? Impressive...
--
Best regards,
Charles
On Thu, 2007-07-19 at 17:24 -0400, Charles Marcus wrote:
On 7/19/2007, Timo Sirainen (tss@iki.fi) wrote:
Is this going to initially be just for attachments? Or for the entire message (not a big deal if it is only attachments, as it is attachments I'm mostly concerned about)?
I think I'll make the dbox format itself support both, but at least initially it's done only for attachments.
By the way... it just occurred to me...
We are talking about Single Instance Storage across the entire namespace, not just on a per dbox file, right?
There will be a configurable location for the storage, so typically you'd set it to same with all users so all users' all dboxes use it.
Will conversion of an existing mail store take place automatically (as users are converted to dbox), or will there be a migration tool of some kind?
Convert plugin can be used to do that. I was thinking about making maildir -> dbox conversion superfast by allowing the maildir files be used directly as dbox files. Only when some dbox metadata needs to be written the file will have to be rewritten into dbox format.
Interesting - so they would auto-self-convert only when necessary?
Yep.
On Thu, 19 Jul 2007 06:37:05 +0300 Timo Sirainen <tss@iki.fi> wrote:
http://dovecot.org/releases/1.1/alpha/dovecot-1.1.alpha1.tar.gz http://dovecot.org/releases/1.1/alpha/dovecot-1.1.alpha1.tar.gz.sig
This is the first alpha release of Dovecot v1.1. I hope that it stabilizes into final release within a few months. There are a lot of new features since v1.0. The most important ones are listed at the end of this post.
Is there an updated Sieve plug-in which works with 1.1?
On Thu, 2007-07-19 at 21:06 -0400, Brad wrote:
Is there an updated Sieve plug-in which works with 1.1?
Here: http://hg.dovecot.org/dovecot-sieve-1.1/
Upgraded to Cyrus Sieve v2.3 so new features include copy and body extensions. There's also include extension but I didn't bother finishing that yet. My body implementation decodes charsets properly (unlike Cyrus), but case-insensitive comparing still works only with ASCII characters.
It requires latest Dovecot hg version to compile though, won't work with alpha1.
On Fri, 2007-07-20 at 10:40 +0300, Timo Sirainen wrote:
On Thu, 2007-07-19 at 21:06 -0400, Brad wrote:
Is there an updated Sieve plug-in which works with 1.1?
Here: http://hg.dovecot.org/dovecot-sieve-1.1/
Upgraded to Cyrus Sieve v2.3 so new features include copy and body extensions. There's also include extension but I didn't bother finishing that yet.
Well, I bothered now. For including global scripts you'll need to add sieve_global_dir setting to protocol lda {}. For including personal scripts the userdb must returned either sieve_dir or home directory.
On Fri, 2007-07-20 at 10:40 +0300, Timo Sirainen wrote:
On Thu, 2007-07-19 at 21:06 -0400, Brad wrote:
Is there an updated Sieve plug-in which works with 1.1?
Here: http://hg.dovecot.org/dovecot-sieve-1.1/
Upgraded to Cyrus Sieve v2.3 so new features include copy and body extensions. There's also include extension but I didn't bother finishing that yet. My body implementation decodes charsets properly (unlike Cyrus), but case-insensitive comparing still works only with ASCII characters.
Headers are also now decoded to UTF-8 before matching.
On Thu, 2007-07-19 at 06:37 +0300, Timo Sirainen wrote:
So, the largest changes I've added to NEWS file (which BTW won't contain changes between alphas/betas/rcs, those will be only in my mailing list posts):
+ SEARCH and SORT finally compare all characters case-insensitively.
We use i;unicode-casemap algorithm.Is in hg now. Also works with Sieve plugin's matching. I've only been wanting to implement this for last 5 years.
BTW. Dovecot is about 5 years old now. I'm not exactly sure what Dovecot's birthday should be. The oldest news items in http://dovecot.org/oldnews.html are:
""" Sat Jul 27 18:14:36 EEST 2002
Second developers release, user authentication actually works now. At least with shadow files, not sure about PAM.
Wed Jul 24 11:13:20 EEST 2002
I think I figured out an ideal solution for the authentication problems. See design.txt, all comments welcome. Updated other parts of it as well. """
Jun 11 I had the thought about writing my own imapd. Jun 15 apparently I began coding it.
Jul 24 was also the day I decided to use Dovecot name. It was suggested to me around Jul 18. I'm pretty bad at naming things myself:
16.06.2002 01:52 <cras> oh - i need a name :) simapd was the only thing i could come up with 16.06.2002 01:53 <cras> first timapd for tiny, but i don't think it will be that tiny..
(s=secure in simapd)
oldnews.html has also some funny stuff:
Sun Nov 24 19:39:31 EET 2002
0.99.0 released. All the major features planned for 1.0 are done now.
Hi all,
BTW. Dovecot is about 5 years old now. I'm not exactly sure what Dovecot's birthday should be. The oldest news items in http://dovecot.org/oldnews.html are:
""" Sat Jul 27 18:14:36 EEST 2002
Even if a bit in advance - happy birthday!!! Timo - thank you for excellent software and best imaginable support!
Jul 24 was also the day I decided to use Dovecot name. It was suggested to me around Jul 18. I'm pretty bad at naming things myself:
I have always been interested how you got around to naming Dovecot. Is there any other meaning intended apart from what the dictionary says (and which seems little related to imap software :)
Best regards,
-- Zbigniew Szalbot
On Fri, 2007-07-20 at 17:24 +0200, Zbigniew Szalbot wrote:
Jul 24 was also the day I decided to use Dovecot name. It was suggested to me around Jul 18. I'm pretty bad at naming things myself:
I have always been interested how you got around to naming Dovecot.
The name came from Mika Boström in IRC (or SILC probably, because I can't find the discussion from my logs). I wasn't sure if I wanted to use it first, but no-one else came up with anything better.
Is there any other meaning intended apart from what the dictionary says (and which seems little related to imap software :)
Pigeons used to carry mail and live in dovecots, so Dovecot is the house for email :)
On Sat, 2007-07-21 at 20:24 +0200, Jakob Hirsch wrote:
Not that it matters much, but isn't it spelled "dovecotE"?
My dictionary suggests both are valid:
Dovecot \Dove"cot\, Dovecote \Dove"cote\, n.
A small house or box, raised to a considerable height above
the ground, and having compartments, in which domestic
pigeons breed; a dove house.
[1913 Webster]
Like an eagle in a dovecote, I
Fluttered your Volscians in Corioli. --Shak.
[1913 Webster]johannes
On Sat, Jul 21, 2007 at 08:42:20PM +0200, Johannes Berg wrote:
On Sat, 2007-07-21 at 20:24 +0200, Jakob Hirsch wrote:
Not that it matters much, but isn't it spelled "dovecotE"?
My dictionary suggests both are valid:
Maybe he's thinking of John Bigboote
mm
participants (9)
-
Brad
-
Charles Marcus
-
Gerhard Wiesinger
-
Jakob Hirsch
-
Johannes Berg
-
Mark E. Mallett
-
Robert Schetterer
-
Timo Sirainen
-
Zbigniew Szalbot