User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:27.0) Gecko/20100101 Firefox/27.0 (Beta/Release) Build ID: 20140218135856 Steps to reproduce: Answered to an email with wrapped and unwrapped (complete) quotations of preceeding mails. The automatic quotiation of the preceeding mail lost its wrapping (in comparison to the message reader window), so I hit "rewrap". Actual results: all newline characters in the quotations of my commincation partner got lost, the quotations of myself (quoted by my communication partner) are wrapped correctly. Expected results: all lines/quotation blocks should be wrapped in the same way or if the lines are wrapped differently (maybe due to a Thunderbird specification) user should be asked what to do (i.e. create an option, ask what to do as long as not default is set or set identical wrapping for every line as default behavior (and don't ask) because the use case in which a user might want to remove all newline from a quotations is fairly rare)

krichter, thanks 4 reporting. testcase message.eml (after removing private data) would be helpful. pls add an attachment above.

krichter, can you pls provide a testcase? save the mixed-wrap msg as .eml file *before* rewrapping, open with text editor, remove private data, then attach at top of this bug

The new status of this bug is RESOLVED/FIXED (see https://bugzilla.mozilla.org/show_bug.cgi?id=1092599 as well)

fixed in 31.2.0

This is an issue again. I'll upload a test case a soon as #1135648 is fixed, because I'm not eager to figure out all the issues I mentioned there for myself.

Do you still see this problem when using version 38? As for your testcase data, it can be protected by using the privacy checkbox on the upload. Then only the folks with trusted security clearance can see your attachment. Or, you can sanitize the private information prior to uploading, as many people do.

> As for your testcase data, it can be protected by using the privacy checkbox on the upload. Not available. As I suggested in As for your testcase data, it can be protected by using the privacy checkbox on the upload. It's not available, but we shouldn't discuss this here, but in #1135648 (the bug reporting guidelines still don't contain a useful statement on privacy).

bug 1433942 has a testcase