Closed Bug 1797101 Opened 2 years ago Closed 2 years ago

When ever I open 107.0b1 (32-bit), this release downloads all email messages even the ones already downloaded.

Categories

(Thunderbird :: Untriaged, defect)

Thunderbird 107
defect

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1796903

People

(Reporter: w.trybula, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:107.0) Gecko/20100101 Firefox/107.0

Steps to reproduce:

I opened Thunderbird (107.0b1 (32 bit)), all email messages on the server immediately download. These downloads included all previously downloaded messages. If I check for emails, I receive another set of all messages on the server. The system indicates I have the latest release on the beta channel.

Actual results:

When I open the latest beta release, it started to download all messages on the server, even those already downloaded. If I check emails, I get another set of all emails on the server. I have seven sets of duplicate emails.

Expected results:

Thunderbird should open and let me download messages. Duplicate messages should not be downloaded when I check for emails. My emails are on a POP server.

Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Resolution: --- → DUPLICATE

I checked out the same email account with the same settings on Thunderbird 102.1.2 (64 bit) after receiving the reply. That email worked as both versions had worked until yesterday morning. Thunderbird loads and does not download until I tell it to. When I click on "Get Messages", the system returns no new messages if those messages have been already downloaded. The 107 beta version will download the same messages again. The question is why did this repeating download of messages start yesterday on the Thunderbird beta? Both version are on different systems running on Windows 10 64bit updated this past week. One system has an intel processor and the other has an AMD one. Thunderbird worked fine on both systems until yesterday morning.. Since that issue is with the beta version, I thought the incident needed to be reported.

Yes, thank you very much for your report.
The problem has already been reported and is already fixed. See Bug 1796903.
The next beta version should work again.

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