If mail contains NULL(0x00), data after NULL is lost upon copy from local folder to local folder, and headers of next mail is displayed. (mismatch between real data length in folder file and mail length in .msf) This bug is "local folder" version of Bug 477799, and is spin-off of Bug 477799 Comment #9 and Bug 482486 Comment #40 & 41. [Steps to produce] 1. Download attached mail box file to Mail directory 2. Copy 4 mails(Select All) to a local folder 3. View mail souce at copy target folder 4. Check mail folder file content of copy target folder. Data generated by copy and phenomenon depended on Tb version. Tb 2.0.0.19(Bug 477799 Comment #9): Mail data after 0x00 was replaced by 0x20. Tb 2.0.0.21: Mail data including 0x00 was copied to target mail folder. No mail data loss when "copy to local folder". i.e. "copy to local folder" case of Bug 477799 is resolved by Tb 2.0.0.21. Tb trunk 2009/5/24 & 2009/5/27 build: (A) mail-1 to mail-3 : data after 0x00 is lost. View source displays top part of next mails too. => Mail offset is correct. => Mail length in .msf is obtained from original mail of copy, instead of really written data length. (B) mail-4(last mail): simply data after 0x00 is lost. Note: Test mail attached to this bug contains 0x00 in mail header. Test mail attached to Bug 482486 Comment #40 contains 0x00 in mail body.

bienvenu says we shouldn't be able to get NULLs by downloading mail, so not blocking.

FYI. As written in Bug 477799, mail with NUL(0x00) was imported from Outlook.