Thunderbird destroys big PDF attachments on opening/saving
Categories
(Thunderbird :: Mail Window Front End, defect)
Tracking
(Not tracked)
People
(Reporter: forum, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:98.0) Gecko/20100101 Firefox/98.0
Steps to reproduce:
Receive a Mail with 7 attachments (1.4MB dwg, 2.8MB pdf, 3.1MB pdf, 3.0MB pdf, 2.0MB dwg, 1.6MB dwg, 14.4MB pdf)
Save all:
See here with screenshots:
https://www.thunderbird-mail.de/forum/thread/89308-thunderbird-zerst%C3%B6rt-anh%C3%A4nge-beim-speichern-aus-gr%C3%B6%C3%9Ferer-mail/?postID=494193#post494193
If i repeat that without the last (14.4MB pdf-file) all files can be saved correctly.
Saving the mail from the same imap-account with another mail-client (tested with opera mail), every attachment is saved correctly.
Imap-Server: cyrus imapd.
Actual results:
Resulting Filesizes:
1.443KB (dwg, OK), 1KB (defekt), 1KB (defekt), 1KB (defekt), 2.071KB (OK), 1.627KB (OK), 1KB (defekt)
Expected results:
all files should have the same size and content as composed.
other users show same issue. It seems to affect only IMAP with disabled synchronisation.
We have the same problem here.
It occures only where IMAP synchronisation is disabled or the options for maximum age and "do not download if message is larger than .." do exclude the message from sychronisation.
If you klick "forward" and open the attachment in the composer window you will get the correct attachment.
E-Mail Server is cyrus imapd.
Same problem with thunderbird 91.9.1 (ubuntu).
The problem doesn't affect PDFs only, here it's an ZIP-file. May be the filetype is of no importance.
There is a solution for the same problem:
https://bugzilla.mozilla.org/show_bug.cgi?id=1589649#c31
Settings for E-Mails up to 40MB :
user_pref("browser.cache.memory.capacity", 40960);
user_pref("browser.cache.memory.max_entry_size", 4000000);
|
||
Comment 5•9 months ago
|
||
Version 115 has at least one major patch in this area, and Version 102 is close to end of life. So if this is a bug it likely won't be patched in version 102. I suggest testing version 115 in three weeks when the update is available and please report your results then.
Resolved per whiteboard
Description
•