Sent Plain text file attachment is corrupted (contains extra spaces)
Categories
(MailNews Core :: Composition, defect)
Tracking
(thunderbird_esr78 affected)
Tracking | Status | |
---|---|---|
thunderbird_esr78 | --- | affected |
People
(Reporter: alfredo.nobili, Unassigned)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
34.11 KB,
application/pdf
|
Details |
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
Comment 1•4 years ago
|
||
Where and how did you check the sent file? In Thunderbird's outbox?
Reporter | ||
Comment 2•4 years ago
|
||
No, both in sent item folder. The recipient confirmed that the file is corrupted.
Reporter | ||
Comment 3•4 years ago
|
||
(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.
Comment 4•4 years ago
|
||
Just to avoid misunderstandings: You successfully checked that your attached file is already corrupted in your own local Sent item folder?
Reporter | ||
Comment 5•4 years ago
|
||
(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).
Updated•4 years ago
|
Comment 6•4 years ago
|
||
(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
Updated•4 years ago
|
Reporter | ||
Comment 7•4 years ago
|
||
(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
Updated•4 years ago
|
Comment 9•4 years ago
|
||
This bug should be closed after bug 1689804 was backed out from ESR and the issue was fixed on beta by bug 1702197.
Updated•4 years ago
|
Description
•