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.

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.

Learn More

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

I am using Thunderbird 102.0.2 (64-bit) and I am still having corrupted emails.

  • 1 reply
  • 3 have this problem
  • 12 views
  • Last reply by christ1

Duane
Duane
more options

I am using Thunderbird 102.0.2 (64-bit) and I am still having corrupted emails.

My emails are sometimes corrupted - link to the wrong emails and/or just see the code not the true email. I try and do a "properties" / "repair folder". Some times it works but most of the time it just sits there and does nothing. I then have to exit Thunderbird and restart it then sometimes the "repair folder" will work. BUT that does not always fix all the corrupted email files.

Any ideas why we are having this issue? I know that there was a problem with an earlier release but I thought it was fixed now.

'''I am using Thunderbird 102.0.2 (64-bit) and I am still having corrupted emails.''' My emails are sometimes corrupted - link to the wrong emails and/or just see the code not the true email. I try and do a "properties" / "repair folder". Some times it works but most of the time it just sits there and does nothing. I then have to exit Thunderbird and restart it then sometimes the "repair folder" will work. BUT that does not always fix all the corrupted email files. ''Any ideas why we are having this issue? I know that there was a problem with an earlier release but I thought it was fixed now.''

All Replies (1)

christ1
christ1
  • Top 25 Contributor
more options

The latest TB version 102.0.2 is still missing fixes to address these problems. There is probably little you can do at this time. An update (v102.0.3) will hopefully be released next week, which should address this problem.