Closed Bug 1705274 Opened 4 years ago Closed 4 years ago

Sent Plain text file attachment is corrupted (contains extra spaces)

Categories

(MailNews Core :: Composition, defect)

defect

Tracking

(thunderbird_esr78 affected)

RESOLVED WORKSFORME
Tracking Status
thunderbird_esr78 --- affected

People

(Reporter: alfredo.nobili, Unassigned)

References

(Regression)

Details

(Keywords: regression)

Attachments

(1 file)

Attached file Screenshot

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:87.0) Gecko/20100101 Firefox/87.0

Steps to reproduce:

Attacched a text file with fixed lenght lines (1900 byte each terminating with CR LF).
(thunderbird version 78.9.1)

Actual results:

Sent file is corrupted. The source of the message sent contains extra spaces (ASCII 20 after the = sign) at EOL making the file not usable.
With version 78.4.3 the file was sent correctly.

Expected results:

Not adding extra spaces

Where and how did you check the sent file? In Thunderbird's outbox?

Flags: needinfo?(alfredo.nobili)

No, both in sent item folder. The recipient confirmed that the file is corrupted.

Flags: needinfo?(alfredo.nobili)

(In reply to Andre Klapper from comment #1)

Where and how did you check the sent file? In Thunderbird's outbox?

No, both in sent item folder. The recipient confirmed that the file is corrupted.

Just to avoid misunderstandings: You successfully checked that your attached file is already corrupted in your own local Sent item folder?

(In reply to Andre Klapper from comment #4)

Just to avoid misunderstandings: You successfully checked that your attached file is already corrupted in your own local Sent item folder?

Yes, the file is corrupted also in the Sent item folder (local).

Summary: Plain text attachment → Sent Plain text file attachment is corrupted (contains extra spaces)

(In reply to alfredo.nobili from comment #0)

Created attachment 9215974 [details]

Attacched a text file with fixed lenght lines (1900 byte each terminating with CR LF).

How do you manage to send that attachment quoted-printable encoded? If I try to do so, it always gets base64 encoded.

Sent file is corrupted. The source of the message sent contains extra spaces

Those spaces are not realy extra spaces. The last line is therefore proportionally shorter.

(ASCII 20 after the = sign) at EOL making the file not usable.

But here they are actually wrong, because TB creates a line break from it when saving.

Regressed by bug 1689804

Component: Untriaged → Composition
OS: Unspecified → All
Product: Thunderbird → MailNews Core
Regressed by: 1689804
Hardware: Unspecified → All
Status: UNCONFIRMED → NEW
Ever confirmed: true

(In reply to Alfred Peters from comment #6)

(In reply to alfredo.nobili from comment #0)

Created attachment 9215974 [details]

Attacched a text file with fixed lenght lines (1900 byte each terminating with CR LF).

How do you manage to send that attachment quoted-printable encoded? If I try to do so, it always gets base64 encoded.

If I set in about:config the flag mail.file_attach_binary to true I get a base64 encoded attachment. With the default value (false) I get a quoted-printable encoded .

Sent file is corrupted. The source of the message sent contains extra spaces

Those spaces are not realy extra spaces. The last line is therefore proportionally shorter.

(ASCII 20 after the = sign) at EOL making the file not usable.

But here they are actually wrong, because TB creates a line break from it when saving.

Regressed by bug 1689804

This bug should be closed after bug 1689804 was backed out from ESR and the issue was fixed on beta by bug 1702197.

Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: