If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Forward a plain text email introduces unwanted EOL or CR characters

UNCONFIRMED
Unassigned

Status

Thunderbird
Untriaged
UNCONFIRMED
5 years ago
5 years ago

People

(Reporter: David Bourguignon, Unassigned)

Tracking

17 Branch
x86_64
Windows 8

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(5 attachments)

(Reporter)

Description

5 years ago
User Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:20.0) Gecko/20100101 Firefox/20.0
Build ID: 20130409194949

Steps to reproduce:

I forwarded a plain text email to someone.


Actual results:

The forwarded text of my plain text email appeared suddenly "jaggy" with unwanted EOL or CR characters creating fake "line feed" effects... As a result, I had to manually remove them, one by one. After this treatment, no more "jagged lines" remained and I forwarded the email without problem.


Expected results:

No extra unwanted characters should be introduced in the original mail... Thanks in advance.
> Actual results:
> The forwarded text of my plain text email appeared suddenly "jaggy"
> with unwanted EOL or CR characters creating fake "line feed" effects.

What kind of phenomenon do you call by "jaggy"?
Phenomenon like bug 611411 comment #0?

> No extra unwanted characters should be introduced in the original mail

Are you talking about inserted space like bug 611411 comment #0?
Or other irrelevant garbled character appears in forwarding mail?

Anyway, to explain problem, I believe mail data of "forwarded/original mail" and "forwarding mail" is far better than words.
Can you attach mail data, if your problem is reproducible?
(1) Save forwarded mail(original mail) to mail-1.eml.
(2) Forward, Send Later.
    At Outbox of Local Folders, save the mail to mail-2.eml.
(3) Edit mail-1.eml and mail-2.eml by Text Editor,
    remove/replace private data in .eml file.
(4) Attach two .eml files to this bug(never paste, please).
(Reporter)

Comment 2

5 years ago
Thanks a lot Wada for your fast reply. I don't know if this bug compares to bug 611411 comment #0 but, as this bug, it definitely changes the way the text flows through paragraphs by inserting new characters.

You will find the files mail-1.eml and mail-2.eml in attachment. For mail-2.eml, the "jagged" appearance is only visible in Thunderbird mail viewer, not in MS Windows Notepad (I guess this confirms the extra EOL/CR hypothesis since I believe Thunderbird follows by default the Unix convention, not the MS Windows one.)

Thanks in advance!
(Reporter)

Comment 3

5 years ago
Created attachment 740182 [details]
Original email
(Reporter)

Comment 4

5 years ago
Created attachment 740183 [details]
Forwarded email
Attachment #740182 - Attachment mime type: application/octet-stream → text/plain
Attachment #740183 - Attachment mime type: application/octet-stream → text/plain
(In reply to David Bourguignon from comment #3)
> Original email
(In reply to David Bourguignon from comment #4)
> Forwarded email

What part of the "Forwarded email" do you call by "unwanted EOL or CR characters" in your bug summary, your "jaggy", your 'fake "line feed" effects', your ""jagged lines", your "extra unwanted characters"?
(Reporter)

Comment 6

5 years ago
Thanks Wada. A picture is worth a thousand words... See in attachment three views, in Thunderbird mail windows, produced by the two emails in attachment.
(Reporter)

Comment 7

5 years ago
Created attachment 740686 [details]
Original email
(Reporter)

Comment 8

5 years ago
Created attachment 740687 [details]
Forwarded email - Top part
(Reporter)

Comment 9

5 years ago
Created attachment 740688 [details]
Forwarded email - Middle part
(In reply to David Bourguignon from comment #6)
> A picture is worth a thousand words...

Message source, and message display. ([SP]=0x20, [CRLF]=0x0D0A])
> --------------------------------------      --------------------------------
> Message Source in format=flowed             Message Display of format=flowed
> --------------------------------------      --------------------------------
> (Original)                                  (Original)
> ...sit amet, fringilla[SP]ac[SP][CRLF]      ...sit amet, fringilla[SP][CRLF]
> nulla.[SP]...                               ac[SP]nulla.[SP]...
> --------------------------------------      --------------------------------
> (Forward)                                   (Forward)
> ...sit amet, fringilla[SP]ac[CRLF]          ...sit amet, fringilla[SP][CRLF]
> nulla.[SP]...                               ac[CRLF]
>                                             nulla.[SP]...
> --------------------------------------      --------------------------------

In Forward mail, [SP] after "ac" just before [CRLF] is ate up, then "ac[CRLF]" is "end of paragraph" in the format=flowed, thus "nulla.[SP]..." is not continued in message display.
IIRC, "eat up white space at end of line" is known phenomenon.
Sorry but I can't recall bug number.

Easiest workaround of this kind of bug in text mail.
  Disable format=flowed use in sending mail.
  mailnews.send_plaintext_flowed = false (default is true)
Is  mailnews.send_plaintext_flowed = false effective workaround in your case?
IIRC, problem was one like next.
  Because excess space is somehow insered at end of line
  perhaps due to bug in some situations,
  logic of "remove the excess space at end of line" was added.
  Then, required space at end of line was removed by the added logic.
(Reporter)

Comment 12

5 years ago
Thanks a lot Wada, but I would like to avoid fixing the bug with a workaround. I would rather find a clean default solution or leave it like that.

One thing is really disturbing: when I reply-to an email, I never encounter such layout problems. Would it be possible to apply the same formatting options in reply-to and forward modes?

Thanks again for your help.
You need to log in before you can comment on or make changes to this bug.