Windows 10 will reach EOS (end of support) on October 14, 2025. For more information, see this article.

Avatar for Username

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.

കൂടുതലറിയുക

This thread was archived. Please ask a new question if you need help.

Saving attachment truncates file extension

  • 1 മറുപടി
  • 1 has this problem
  • 1 കാഴ്ച
  • Last reply by AgnesRM

rwallinger
rwallinger
more options

I'm working on Windows 10 Home x64, and just updated Thunderbird to the latest version available(91.70). When I get an email with a .JPG attachment, or a .PNG, when saving the file by dbl clicking the attachment name at the bottom of the email, when I rename it, it saves with a truncated file extension. Say the file is test.jpg, when I save it, I end up with test.pg. When I tried test.png I ended up with test.ng.

If I leave the file name the same as comes in the email, it saves fine. If I use the save as function at the bottom right for the attachment I can save the file fine, and I can even rename it here. What's going on? I've replicated this on 2 different machines.

Anyone have any ideas?

I'm working on Windows 10 Home x64, and just updated Thunderbird to the latest version available(91.70). When I get an email with a .JPG attachment, or a .PNG, when saving the file by dbl clicking the attachment name at the bottom of the email, when I rename it, it saves with a truncated file extension. Say the file is test.jpg, when I save it, I end up with test.pg. When I tried test.png I ended up with test.ng. If I leave the file name the same as comes in the email, it saves fine. If I use the save as function at the bottom right for the attachment I can save the file fine, and I can even rename it here. What's going on? I've replicated this on 2 different machines. Anyone have any ideas?
Attached screenshots

എല്ലാ മറുപടികളും (1)

AgnesRM
AgnesRM
more options

This earlier answer may be the same issue you are seeing? If so, a bug has been reported. https://support.mozilla.org/en-US/questions/1364343