Closed Bug 1777387 Opened 2 years ago Closed 2 years ago

V102 Upgrade downloaded all messages again, causing duplicates (POP, messages left on server until deleted by client)

Categories

(MailNews Core :: Networking: POP, defect)

Thunderbird 102
defect

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: fharris, Unassigned)

References

(Blocks 1 open bug)

Details

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

Steps to reproduce:

Upgraded to Thunderbird V102

Actual results:

The upgrade to V102 didn't sync the messages between client PC and server. All messages on the server were downloaded again causing thousands of additional/duplicated messages. My solution was to remove all messages from the server before upgrading.

Setup: Using POP3 protocol - messages are left on the server until deleted by the client. Mailboxes are on a cPanel server.

Flags: needinfo?(fharris)
Summary: V102 Upgrade Duplicated Messages → V102 Upgrade Can Duplicate Messages
Flags: needinfo?(fharris)
Blocks: tb102found
Component: Untriaged → Networking: POP
Product: Thunderbird → MailNews Core
Summary: V102 Upgrade Can Duplicate Messages → V102 Upgrade downloaded all messages again, causing duplicates (POP, messages left on server until deleted by client)
See Also: → 1778037
See Also: → 1779296

fharris, does this still reproduce with 102.2.2 ?

Flags: needinfo?(fharris)
Whiteboard: [closeme 2022-10-01]

I have not seen the problem again.

Flags: needinfo?(fharris)

Thanks for the update

Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Resolution: --- → WORKSFORME
Whiteboard: [closeme 2022-10-01]

Running TB 102.2.2...

But I DO see duplicates -- the entire content of the server mailbox, in my case dozens, not thousands -- whenever I use the GET MESSAGES button. Any account at a random time will suddenly have its contents automatically downloaded if connected to GM, and might fetch duplicates on a manual poll.

I've only "upgraded" to TB 102.0.0 (from 98.10.0) the one time, where I first witnessed the issue. I have since "upgraded" incrementally through all official release versions of TB 102.x.x and the problem persists to this day. (Haven't seen it on a manual poll in the current version, but they are rare, and I've only just installed this one.)

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