This message is to announce the release of the University of Washington IMAP
toolkit version 2006 (imap-2006).

This is a major release, and has a change of license: imap-2006 is released
under the Apache License, Version 2.0.

Programs written for the previous version (imap-2004g) should build with this
version with minor or no modification. Third-party mailbox format drivers
written for the previous version will require modification to handle UIDPLUS.

The most important end-user visible changes in imap-2006 that affect UW imapd
are as follows:

imap-2006 contains support for the new mix format. This is a dual-use mailbox
format designed for performance and reliability with large mailboxes. Compared
to previous formats, mix has the following characteristics:
. greater robustness; many failures are "self-healing"
. fewer risky random-access I/O operations
. greater performance
. furture extensibility for new IMAP capabilities.

imap-2006 contains major extensions to its Unicode support. Searching and
sorting are now done with strings canonicalized to titlecase and decomposed
form. Among other things, this means that Latin letters with diacriticals
will now sort with the basic Latin letter, and case-independent searching of
such letters (e.g., German umlauts) now works. Previously, sorting was done
strictly by Unicode codepoint, and case-independence only worked with ASCII.

imapd now supports the IMAP UIDPLUS extension, and is compliant with RFC 4315.

Memory management in several mailbox formats has been redesigned, and imapd
will now consume less memory and be faster in those formats.



The following changes will show up in clients rebuilt to use imap-2006. In
particular, the imap-2004g code in Pine 4.64 can be replaced with imap-2006 by
deleting the existing pine4.64/imap directory and replacing it with the
imap-2006 files.

As noted above, support for mix and extended Unicode support.

UNIX SSL/TLS certificate validation now supports certificate alternative names.

The new /tls-sslv23 flag in a mailbox name causes a TLS session to use the
(incorrect) SSLv23 client method instead of the TLSv1 client method. Some
broken servers use the SSLv23 server method, and this flag works around that
problem. WARNING: use of this flag will cause TLS negotiation to fail with
a server which uses the proper TLSv1 server method. Additionally, there are
known security risks in SSLv2; so users should be suspicious if this switch
suddenly becomes necesary.

-- Mark --

http://staff.washington.edu/mrc
Science does not emerge from voting, party politics, or public debate.
Si vis pacem, para bellum.

> Science does not emerge from voting, party politics, or public debate.

Perhaps not, but funding for it does...