User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130 An empty line shown when composing the message, will not show in a copy in the sent folder, or a copy sent to self. It will show in "message source", and show in other email clients (Outlook, etc). Reproducible: Sometimes Steps to Reproduce: 1. Unsure, seems to happen during lots of editing of lines (spacing, backspacing, deleting, line return). Actual Results: It shows an empty line as desired, but later doesn't show. Expected Results: Always display the line. I've seen it happen from 0.99 through 1.2.1, so I thought it was about time to submit. :) I haven't had much luck figuring out how to reproduce the problem, but I will submit a .eml file from mozilla showing the problem clearly.

The message has been edited for privacy reasons. This message was composed as "first line", then an empty line, then "second line". It now displays (in preview pane, or in its own window) as "first line", then "second line", with no empty line. In the message source it shows the empty line. I also tried Outlook Express (5.50) and it also displays the empty line. All my preferences are default, except maybe: -"Compose Messages In HTML Format" was disabled when composing the message. -"Prefers to receive messages formated as" was set to "unknown" for all receipents. -"Send the message in both plain text and html" was chosen.

Very odd, but the attached file behaves as described, in 1.4RC2 Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030612 It also shows without the blank line if the .EML file is opened in the browser. A look a the hex dump of the file shows the expected (under Windows) 0D0A0D0A sequence between the two lines. Incidentally, "Send the message in both plain text and html" wouldn't have come into play because there was no HTML formatting in the message.

Just wanted to mention that at 1.5 RC2, the bug is still there. It definitely occurs when doing large amounts of editing. This usually means I'm working on an important message that I want to get perfect, and then after I send, I check my sent copy, and see the extra/missing lines which makes me quite upset. :p

*** Bug 241375 has been marked as a duplicate of this bug. ***

Stumbling across this bug again. The display issue is completely understandable: the message has Content-Type: text/plain; format=flowed and f=f means that the trailing space(s) at the end of the first line cause the subsequent (blank) line to be reflowed onto the end. How this message was generated is a bit more of a puzzle. Normally, with plain text mail composition, spaces at the end of a line followed by a hard break are stripped from the text. If composed with the HTML editor, there is a known problem (bug 125928) where this does not happen -- but reporter says that he was composing as plain. However, I recently encountered bug 261467, which is about this same problem with the plain text editor if the wrap column for the editor is set to zero. Jason Jackson, can you confirm that you have that setting? If so, please dupe this bug to that one.

No response from reporter, duping. *** This bug has been marked as a duplicate of 261467 ***

Jason Jackson: regarding your comment in the duplicate bug: First of all, if you don't think this bug is the same as that one, then comment in *this* bug. I tried to make comment 5 as understandable as possible. I concede that the underlying technicalities are obscure. I asked what I thought was a simple question: what is your setting (the value of xxx) for: Preferences | Mail & Newsgroups | Composition Wrap plain text messages at [xxx] characters ? If the value is 0, then this bug is most assuredly a duplicate of that one. If it is *not* 0, please state what it is, and feel free to reopen the bug.

You're correct, my "Wrap plain text messages" is set at 0. I've set it to the apparent default of 72, and I'll keep an eye out for my bug to reappear. I must of set this years ago in the Netscape days (before Mozilla 1.0). I don't know how I missed your original request. Thankfully there's vigiliant guys like you to make sense of thousands of reports from people with a little less sense like myself. My congratulations to you. This might not be the correct forum for this, but I'm curious, the fact that this happens with a setting of 0, is it still a bug? What's the proper way to compose unwrapped plain text messages?