Open
Bug 842524
Opened 12 years ago
Updated 6 months ago
Connection timeout during large archiving results in duplicated imap messages
Categories
(MailNews Core :: Networking: IMAP, defect)
Tracking
(Not tracked)
UNCONFIRMED
People
(Reporter: mcicogni, Unassigned)
Details
(Keywords: dupeme)
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:18.0) Gecko/20100101 Firefox/18.0
Build ID: 20130201065344
Steps to reproduce:
I have an IMAP account that is configured to keep its Archives within Local Folders (the usual quota reasons on the server).
While archiving ~1000 messages from last year, and when about 320 messages had been successfully downloaded, the connection was reset for connectivity issues. The archiving operation stopped and no message was deleted from the IMAP folder.
Then, I restarted the archiving process from the beginning. I expected TB to be able to detect it had already downloaded several hundred messages, and that it would skip them.
Actual results:
TB started downloading all messages from the beginning again, resulting in a second copy of each message being stored in Local Folders.
Expected results:
TB should have detected that those messages had been downloaded already, and skipped them.
Reporter | ||
Updated•12 years ago
|
Whiteboard: IMAP archive duplication
Updated•12 years ago
|
Summary: Connection timeout during archiving results in duplicated messages → Connection timeout during archiving results in duplicated imap messages
Whiteboard: IMAP archive duplication → [dupeme?
Updated•3 years ago
|
Severity: normal → S3
Updated•2 years ago
|
Component: Untriaged → Networking: IMAP
Product: Thunderbird → MailNews Core
Version: 17 Branch → 17
Updated•6 months ago
|
Keywords: dupeme
Summary: Connection timeout during archiving results in duplicated imap messages → Connection timeout during large archiving results in duplicated imap messages
Whiteboard: [dupeme?
You need to log in
before you can comment on or make changes to this bug.
Description
•