This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Problem with large attachments in Thunderbird

more options

Using Thunderbird 102.4.0 (64-bit) on Linux as well as on Windows 10. I receive an email with a large (26MB) PDF file attached. I connect to the server using IMAP and open the email. When I try to open the attachment it shows as a blank page. I try to save the attachment as a PDF file to disk and it is created as a 27-byte file. Without closing Thunderbird, I save the complete email to disk as a .eml file. I then open the .eml file with the same instance of Thunderbird, and, from that window, I am able to correctly open as well as save to disk the PDF file that was attached. This shows that the email as received by the mail server was not corrupted and that the problem is in Thunderbird.

The problem happens on both Linux and Windows, and with several different emails.

Using Thunderbird 102.4.0 (64-bit) on Linux as well as on Windows 10. I receive an email with a large (26MB) PDF file attached. I connect to the server using IMAP and open the email. When I try to open the attachment it shows as a blank page. I try to save the attachment as a PDF file to disk and it is created as a 27-byte file. Without closing Thunderbird, I save the complete email to disk as a .eml file. I then open the .eml file with the same instance of Thunderbird, and, from that window, I am able to correctly open as well as save to disk the PDF file that was attached. This shows that the email as received by the mail server was not corrupted and that the problem is in Thunderbird. The problem happens on both Linux and Windows, and with several different emails.

All Replies (3)

more options

Hello there eduardo ubelman. We have read your message. We try to help you.

your message was received on your Thunderbird version 102.04 as stated with your message sent to us. If it had the regular extension to receive it, it will be there to process the message.


https://support.mozilla.org/en-US/kb/how-use-attachments


Greetings Firefox volunteer.

Googlethunderbird trɔe

more options

Hello there eduardo ubelman.



The subject of you upon receipt of messages containing this content but not being played into a visible message in your folder.

The problem that there would be because these messages do end up in your file folder on your hard drive in the form of .eml can be correct.

These types of problems are usually resolved internally by Thunderbird in the short term . It would then be automatically resolved within a time frame.

Also to be able to solve this problem and it is not seen as a permanent issue and they are not aware of it today, there are also several steps that you can take yourself if a solution is not immediately implemented by Thunderbird bug section.

I will add these steps in our topic where we are looking for a solution together today.

The first method is to repair the folder in question. You can run this folder with the right mouse button and choose repair folder from the drop-down menu.

The subject is called repair folder.

the second method is to make the choice to delete the .msf files from the respective folder in question.

https://support.mozilla.org/en-US/kb/how-can-i-send-large-attachment


Greetings Firefox volunteer

Googlethunderbird trɔe

more options

This does not solve the problem. I created a NEW email folder. I copied the email into that new folder at the server - so I know the new folder is not corrupted. I opened the copy of the email in this new folder and had the same problem. I then deleted the .msf file for the new folder and tried again. The attachment is still saved as a 27 byte file instead of the 26MB it really has.