Important Notice: We're experiencing email notification issues. If you've posted a question in the community forums recently, please check your profile manually for responses while we're working to fix this.

On Monday the 3rd of March, around 5pm UTC (9am PT) users may experience a brief period of downtime while one of our underlying services is under maintenance.

Sök i support

Akta dig för supportbedrägerier: Vi kommer aldrig att be dig att ringa eller skicka ett sms till ett telefonnummer eller dela personlig information. Rapportera misstänkt aktivitet med alternativet "Rapportera missbruk".

Läs mer

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

  • 1 svar
  • 3 har detta problem
  • 2 visningar
  • Senaste svar av christ1

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.''

Alla svar (1)

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.