http://dovecot.org/releases/2.2/dovecot-2.2.3.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.3.tar.gz.sig This is a pretty important upgrade for v2.2 users, because of the IMAP ENVELOPE reply fix. * LDA/LMTP: If new mail delivery first fails with "temporary failure", tempfail the whole delivery instead of falling back to delivering the mail to INBOX. (Requires new Pigeonhole as well.) * doc/solr-schema.xml was updated to Solr v4.x format. Also the default analyzers were changed, hopefully for the better. Note that the schema can't be changed for existing Solr indexes without rebuilding everything. * Solr plugin does only soft commits from now on. You'll need a cronjob to send a hard commit command to it every few minutes. + Added %N modifier for variables as %H-like "new hash" + sdbox, mdbox: Support POP3 message order field (for migrations) + Added mailbox { driver } to specify a different mail storage format for the mailbox than generally used within the namespace. + Added initial lib-sasl library for client side SASL support. Currently supports only PLAIN, LOGIN and plugins. Used currently by IMAP and POP3 proxying when authenticating to the remote server. - IMAP: If subject contained only whitespace, Dovecot returned an ENVELOPE reply with a huge literal value, effectively causing the IMAP client to wait for more data forever. - IMAP: Various URLAUTH fixes. - imapc: Various bugfixes and improvements - pop3c: Various fixes to make it work in dsync (without imapc) - dsync: Fixes to syncing subscriptions. Fixes to syncing mailbox renames.
On 17.6.2013, at 0.41, Timo Sirainen <tss@iki.fi> wrote:
http://dovecot.org/releases/2.2/dovecot-2.2.3.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.3.tar.gz.sig
This is a pretty important upgrade for v2.2 users, because of the IMAP ENVELOPE reply fix.
sdbox/mdbox users: Don't upgrade just yet.. It seems it may cause "Extension header update points outside header size" errors that don't fix themselves. (Bug 1: Causing this error in the first place, bug 2: not being able to fix it automatically.) If you're already getting those errors, attached a workaround patch. Probably happens only to POP3 users. I'm not sure yet how to reproduce this.
participants (1)
-
Timo Sirainen