Этот сайт имеет ограниченную функциональность, пока мы проводим техническое обслуживание для улучшения его работы. Если какая-либо статья не решила вашу проблему и вы хотите задать вопрос, наше сообщество поддержки ждёт вас: @FirefoxSupport в Твиттере и /r/firefox на Reddit.

Поиск в Поддержке

Избегайте мошенников, выдающих себя за службу поддержки. Мы никогда не попросим вас позвонить, отправить текстовое сообщение или поделиться личной информацией. Сообщайте о подозрительной активности, используя функцию «Пожаловаться».

Подробнее

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

  • 1 ответ
  • 3 имеют эту проблему
  • 12 просмотров
  • Последний ответ от 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.''

Все ответы (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.