From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20010913 BuildID: 2001091303 If someone sends me an e-mail message that was not wrapped by their user agent, when replying, Mozilla does not wrap the quote according to my settings unless I manually re-wrap the message from the options menu. Mozilla already (by default) wraps un-wrapped messages when forwarding messages using the 'inline' option. It should do the same when dealing with replying. Or, at least have an option to function that way. Reproducible: Always Steps to Reproduce: 1. Open a plain-text message sent to you that is unwrapped. You can verify this by viewing the message source. 2. Click reply 3. Change "To:" to yourself 4. Hit send 5. Open the message 6. View message source to verify quoted msg is unwrapped Actual Results: The message will remain unwrapped (even during composition) and be sent to the recipient regardless of any wrapping options set in composition preferences, unless you manually re-wrap the composition from the options menu. Expected Results: Mozilla should automatically re-wrap the quoted text when replying as if the Options->Rewrap command was chosen. This would be consistent with what is done when forwarding a message. Additional: Note that I am talking about Mozilla's behavior to the physical message. When viewing plain-text mail with Mozilla, by default it will automatically display the message wrapped. However, if I were replying to someone using a user agent that does not display the message wrapped, his quote will appear unwrapped, even though I have in my Mozilla composition options, "wrap plain text messages at [xx] characters."

Sounds similar to 83378.

Is this the same as, when replying, the message is not quoted but rather the same as if it was just "viewed" or "edited as new". I have to cut the message and then "insert as quote" to get appropriate reply behavoir. Just started within the last day.

dup of bug 83378?

I am not sure I understand this correctly, but I think this is bug 110754. pi

Nobody seems to disagree. pi *** This bug has been marked as a duplicate of 110754 ***

v