On 2010-11-02 17:56, Julien Cristau wrote:
On Mon, Nov 1, 2010 at 09:07:39 +0000, Paul J Stevens wrote:The new version currently in unstable fixes quite a few bugs. The new upstream release is a maintanance-only bugfix-only release.Any chance you could list those bugs? It's getting late in the freeze for non-targetted updates, and this update is quite big.
Julien, thanks for looking into this. I assume you're asking about the upstream bugs fixed, since the debian changelog already mentions debian bugs.
Upstream changes in dbmail-2.2.17 since 2.2.11. Summary:Several important IMAP fixes, mostly IMAP compliance and performance related. A critical POP3 fix. IPv6 support. And finally some additional small non-critical fixes.
The full list: 2.2.17 - Slow IMAP results and high CPU usage when message_idnr is very big - IMAPD uses 100% CPU if some file was attached to mail during IMAP APPEND - IMAPD sends spurious ')\r\n' after message 2.2.16 - stack smashing in usermap code 2.2.15 - dbmail-smtp segfault with To field with "unlisted-recipients" - Segfault after PASS in POP3 - messages marked as read during IMAP EXAMINE mailbox 2.2.14 - buggy md5 implentation causes sieve generated autoresponders to fail - Incoming IP addresses missing in syslog - fix postgresql-8.4.2 issues 2.2.13 was a botched release. 2.2.12 - IPv6 support - fix for duplicate mailboxes in LIST/LSUB responses - internaldate as UTC - fix file descriptor leakage -- ________________________________________________________________ Paul Stevens paul at nfg.nl NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31 The Netherlands________________________________http://www.nfg.nl