[Dovecot-news] v1.2.2 released

hehachris

Verified User
Joined
Nov 24, 2004
Messages
598
Location
Hong Kong
http://dovecot.org/releases/1.2/dovecot-1.2.2.tar.gz
http://dovecot.org/releases/1.2/dovecot-1.2.2.tar.gz.sig

Found and fixes several v1.2-specific bugs. Hopefully it's now stable
for most people's usage.

* GSSAPI: More changes to authentication. Hopefully good now.
* lazy_expunge plugin: Drop \Deleted flag when moving message.

+ dovecot -n/-a now outputs also lda settings.
+ dovecot.conf !include now supports globs (e.g.
!include /etc/dovecot/*.conf). Based on patch by Thomas Guthmann.
+ acl: Support spaces in user/group identifiers.
+ shared mailboxes: If only %%n is specified in prefix, default to
current user's domain.
- Dovecot master process could hang if it received signals too rapidly.
- Fixed "corrupted index cache file" errors (and perhaps others) caused
by e.g. IMAP's FETCH BODY[] command.
- IMAP: When QRESYNC is enabled, don't crash when a new mail is
received while IDLEing.
- IMAP: FETCH X-* parameters weren't working.
- Maildir++ quota: Quota was sometimes updated wrong when it was
being recalculated.
- Searching quoted-printable message body internally converted "_"
characters to spaces and didn't match search keys with "_".
- Messages in year's first/last day may have had broken timezones
with OSes not having struct tm->tm_gmtoff (e.g. Solaris).
- virtual plugin: If another session adds a new mailbox to index,
don't crash.
 
Dovecot should move to a time-based release schedule. The update frequency is too high right now.
 
Personally, I think it's great they take their product seriously enough to keep it secure and working well with these new releases. If you want a "time release" schedule, then make your own. Update it every 6 months. They aren't forcing anyone to update to the latest version.

Would you rather have it stable and secure, or unsecure by having them wait until a specific time to release a patch for a bug that is several months overdue? It's your decision ultimately, but I really don't mind updating considering it takes all of 30 seconds.

Just my 2 cents.
 
Personally, I think it's great they take their product seriously enough to keep it secure and working well with these new releases. If you want a "time release" schedule, then make your own. Update it every 6 months. They aren't forcing anyone to update to the latest version.

Would you rather have it stable and secure, or unsecure by having them wait until a specific time to release a patch for a bug that is several months overdue? It's your decision ultimately, but I really don't mind updating considering it takes all of 30 seconds.

Just my 2 cents.

The thing is that they usually mix bug fixes with new features. This combined with no extensive testing means that we as users basically are their QA-team. That's not proper release management. By time-based releases I mean releases of new features. This also helps for proper planning concerning QA. Bugs and security issues obviously needs fixing ASAP.
 
Back
Top