Closed Bug 1778111 Opened 3 years ago Closed 3 years ago

Since updating from 91 to 102 Thunderbird constantly has to rebuild junk & trash folders (NOT better in 102.0.3)

Categories

(Thunderbird :: Folder and Message Lists, defect)

Thunderbird 102
defect

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: mike, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: regression)

User Agent: Mozilla/5.0 (Windows NT 6.1; rv:91.0) Gecko/20100101 Firefox/91.0

Steps to reproduce:

After upgrade the problem started. Thunderbird was configured to download messages at start up. I would start Thunderbird.

Actual results:

Junk filters stopped working because the Junk folder was not recognized and the junk remained in the Inbox. I would get a error message stating that the message filter could not be executed. When the Junk folder was clicked, the general account screen appeared and the folder rebuilt itself. Then it worked. The same thing happened with Trash. This did not happen with 91. It does not appear to be an isolated instance, as it has happened several times in the last few days. As a work around I unchecked "download messages at start up" and click each folder to make sure it is functional after the program starts.

Expected results:

All folders should be fully functional at startup. Thunderbird should run through a start up diagnostic to make sure the critical folders are functional and rebuild those that are not before the program opens.

Blocks: tb102found

I should have mentioned that what was happening was the summary files were being rebuilt. This happens virtually every time I start Firefox.

The 102.0.1 patch did not improve the situation. Some of the MSF files still rebuild after start-up causing files that were placed in junk by filters or manually and those deleted into trash to copy back into the inbox. The folders that seem to rebuild are the inbox, trash and junk. This creates a second copy of the message. A work around that appears to work is to shift delete the messages. That seems to prevent a second copy when the MSF rebuilds.

Keywords: regression
Summary: Since updating from 91 to 102 Thunderbird constantly has to rebuild junk & trash folders → Since updating from 91 to 102 Thunderbird constantly has to rebuild junk & trash folders (NOT better in 102.0.1)

102.0.2 did not fix the bug. When I open TB in the morning the MSF for Trash and Junk always has to rebuild. Very often the Inbox rebuilds. The end result is that what was junk yesterday now appears duplicated in the inbox. Even if I shift deleted the emails the day before, some or all of them reappear in the Inbox. So, every morning I have to rebuild the folders and clean up my inbox before getting new messages. I typically leave action items in the inbox, so in the morning I have to check for duplicate messages so I can delete one and save the other. I'm afraid that if I do not shut the program down at the end of each day, I may end up with several day's worth of junk back in my inbox.

102.03 did not fix the bug. It appears that every time Thunderbird opens any folder that had activity in the previous session it rebuilds the MSF. Prior to getting new mail, any emails that were in the junk folder the from the previous session, even if they were deleted, appear back in the inbox.

Summary: Since updating from 91 to 102 Thunderbird constantly has to rebuild junk & trash folders (NOT better in 102.0.1) → Since updating from 91 to 102 Thunderbird constantly has to rebuild junk & trash folders (NOT better in 102.0.3)

I'd like to reverse my last comment, it does seem that 102.0.3 may have corrected the problem as it hasn't occurred for 2 days. Thanks!

Thanks for the update!

Status: UNCONFIRMED → RESOLVED
Closed: 3 years ago
Resolution: --- → WORKSFORME

I don't use "download messages at start up", but even in TB 102.0.3, I still regularly see TB rebuilding the Summary Files for INBOX and TRASH when I click on them. As usual, not every time (and not immediately after having done it), but often enough to be a problem.

Haven't had a problem for a week, so I think this bug is squarshed. Thanks for fixing it!

You need to log in before you can comment on or make changes to this bug.