Last Comment Bug 277154 - Wrap text for non HTML emails not working at all
: Wrap text for non HTML emails not working at all
Status: RESOLVED DUPLICATE of bug 277153
Product: SeaMonkey
Classification: Client Software
Component: MailNews: Message Display (show other bugs)
: 1.7 Branch
: x86 Windows XP
-- normal (vote)
: ---
Assigned To: (not reading, please use instead)
Depends on:
  Show dependency treegraph
Reported: 2005-01-05 10:25 PST by sturges
Modified: 2005-01-05 10:41 PST (History)
0 users
See Also:
Crash Signature:
QA Whiteboard:
Iteration: ---
Points: ---


Description User image sturges 2005-01-05 10:25:17 PST
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a6)
Gecko/20041210 and prior versions.

As reported in associated bugs 155622 and 274168 there are problems with the
wrap text.

I have discovered that Mozilla lies about the formatting of the emails that are
composed using the Html editor and sent as "Send as Plain Text Only
(Recommended)", this is why I submit a new bug.

What actually happens is Mozilla inserts line breaks after about 72 characters
in the outgoing email regardless of any settings [see tests below]. 

When previewing the sent emails, or opening them, Mozilla pretends it hasn't
inserted these line breaks but if you do a CTL+U you get the real story.

After composing an email with the desired line breaks in the correct places
Mozilla inserts so many line breaks that it makes a nonsense of reading the text
at the other end.

Even Netscape 4.7x did not have this problem.

Tests performed:
From an email composition window do Edit | Preferences | Mail & Newsgroups |
Using the setting "Wrap plain test messages at 0 characters" and "Wrap plain
test messages at 1000 characters" - the result is the same.


1) Mozilla inserts uncontrollable line breaks in outgoing emails.
2) Mozilla renders emails differently from what is actually received or sent.
Comment 1 User image Oliver Klee 2005-01-05 10:41:06 PST

*** This bug has been marked as a duplicate of 277153 ***

Note You need to log in before you can comment on or make changes to this bug.