http://dovecot.org/releases/dovecot-1.0.rc18.tar.gz http://dovecot.org/releases/dovecot-1.0.rc18.tar.gz.sig I think we're quite near v1.0 now. * ACL plugin + Maildir: Moved dovecot-acl file from control directory to maildir. To prevent accidents caused by this change, Dovecot kills itself if it finds dovecot-acl file from the control directory. * When opening a maildir, check if tmp/'s atime is over 8h old. If it is, delete files in it with ctime older than 36h. However if atime - ctime > 36h, it means that there's nothing to be deleted and the scanning isn't done. We update atime ourself if filesystem is mounted with noatime. * base_dir doesn't need to be group-readable, don't force it. * mail_read_mmaped setting is deprecated and possibly broken. It's now removed from dovecot-example.conf, but it still works for now. * Removed also umask setting from dovecot-example.conf since currently it doesn't do what it's supposed to. + Authentication cache caches now also userdb data. + Added mail_log plugin to log various mail operations. Currently it logs mail copies, deletions, expunges and mailbox deletions. - dict quota: messages=n parameter actually changed storage limit. - A lot of fixes to handling index files. This should fix almost all of the problems ever reported. - LDAP: auth_bind=yes was more or less broken. - Saved mails and dovecot-keywords file didn't set the group from dovecot-shared file. - Fixed potential assert-crash while searching messages - Fixed some crashes with invalid X-UID headers in mboxes - If you didn't have a namespace with empty prefix, giving STATUS command for a non-existing namespace caused the connection to give "NO Unknown namespace" errors for all the future commands. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part Url : http://dovecot.org/pipermail/dovecot-news/attachments/20070122/63e06c22/attachment.pgp
Timo Sirainen wrote:> http://dovecot.org/releases/dovecot-1.0.rc18.tar.gz > http://dovecot.org/releases/dovecot-1.0.rc18.tar.gz.sig > > I think we're quite near v1.0 now.> + Added mail_log plugin to log various mail operations. Currently it > logs mail copies, deletions, expunges and mailbox deletions.Just a suggestion... maybe put a freeze on new features and stabilize 1.0 with the current feature set and a known-bugs list. The config file has already been revised several times throughout the RC series, so maybe that means that too much development is happening under a "release candidate" banner? I'm looking at this from a production admin's point of view: It's getting somewhat amusing to see more and more RCs, when the core functionality is pretty much "done". Problem is, RCs are not really preferred for a production deployment in the eyes of nontechnical people. What a production environment needs is a nailed down version that doesn't change features and only puts in critical fixes. From what I can see, dovecot could have released a 1.0 two or three RCs ago and released bugfixes via a 1.0.1, 1.0.2, etc. branch, with new development in a 1.1-beta line. Timo, we believe in your code... it works... so *please* slap a real release number on it, and we can finally convince others that it's time to switch. :) -- -- Todd Vierling <tv at duh.org> <tv at pobox.com> <todd at vierling.name>