http://dovecot.org/rc/ Two backports from 1.0-tests and pretty important fix for mbox users if you're not already filtering X-UID header somewhere. For 1.0-tests you can fix it for now by applying patches http://dovecot.org/list/dovecot-cvs/2005-January/004046.html and http://dovecot.org/list/dovecot-cvs/2005-January/004047.html - Message address fields are now parsed differently, fixing some issues with spaces. Affects only clients which use FETCH ENVELOPE command. - Message MIME parser was somewhat broken with missing MIME boundaries - mbox: Don't allow X-UID headers in mails to override the UIDs we would otherwise set. Too large values can break clients and possibly Dovecot itself. -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 186 bytes Desc: This is a digitally signed message part URL: <http://dovecot.org/pipermail/dovecot/attachments/20050119/a3d7453d/attachment-0001.bin>
On 19.1.2005, at 02:16, Timo Sirainen wrote:> - mbox: Don't allow X-UID headers in mails to override the UIDs we > would otherwise set. Too large values can break clients and > possibly Dovecot itself.Looks like Dovecot itself doesn't break: Error: Reached maximum UID in mailbox mail/.imap/INBOX/.imap.index, rebuilding index Then it will reassign new UIDs for mails. 1.0-tests don't do that anymore, have to fix that some day. Thunderbird and probably several others will break with UIDs larger than 2^31 because they use signed integers to store UIDs. That could be considered a bug, since IMAP RFC specifies UIDs are 32bit.. -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 186 bytes Desc: This is a digitally signed message part URL: <http://dovecot.org/pipermail/dovecot/attachments/20050119/44dc9220/attachment-0001.bin>