On Sat, May 12, 2007, Anne <[EMAIL PROTECTED]> said: >>> TB and Squirrelmail try to display them in ISO and show awful stuff. >>> >> >> Yes, that's a known bug. Those values need to be encoded back into utf7 >> before sending them to the client. >> >> This most likely won't get fixed in 2.2.5, but is on the top of bug >> priorities. Making dbmail multi-charset enabled in all storage engines >> and in the imap layer has been a long journey already. We're nearing the >> end. >> >> > > Does this mean when someone is still at 2.2.2, one should wait for 2.2.6 ?
The encoding issues won't be a regression in 2.2.5, just an ongoing issue that will take too long to fix to meet the intended schedule. Something Paul may need to clarify is if there will be any differences in how data is stored in 2.2.2 vs. the upcoming 2.2.5 -- would there be a problem if a site upgraded to 2.2.5, found bugs, then reverted back to 2.2.2? Aaron _______________________________________________ DBmail mailing list [email protected] https://mailman.fastxs.nl/mailman/listinfo/dbmail
