Closed Bug 1829077 Opened 3 years ago Closed 3 years ago

imap mail fetch clears and reloads the entire INBOX in a loop

Categories

(MailNews Core :: Networking: IMAP, defect)

Thunderbird 102
x86_64
macOS
defect

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: aathan_github, Unassigned)

Details

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/112.0.0.0 Safari/537.36

Steps to reproduce:

At some unknown exact point but over the last few days, Thunderbird on my Mac OS X box, which has IMAP servers defined (services provided by courier IMAP) will, without provocation, re-download the entire INBOX. I have 170k+ messages in this inbox so this is extremely time consuming and renders Thunderbird almost unusable

Actual results:

Thunderbird will sometimes be using 100% CPU and be stuck in the middle of downloading the INBOX, and I need to quit and restart it (sometimes but not always with a force quit). Once I restart Thunderbird it will begin fetching from 0. The Message list clears when this happens and then slowly fills back in as the index is downloaded.

Expected results:

stable fetch of the inbox

Forgot to mention that I tried deleting this inbox from ~/Library/Thunderbird and after that, the download terminated and did not loop, at least for a few hours. However, I have no idea if it was because of my action or just random chance, as it is now re-downloading my entire inbox again.

This was due to a full disk condition on the IMAP server. However, perhaps there is a way for Thunderbird to issue a warning or error to the user when the IMAP server seems to not be remembering the UIDV / or seems to be re-indexing constantly??

OS: Unspecified → macOS
Hardware: Unspecified → x86_64

If the IMAP server has full disk and returning nonsense due to that, it's unlikely things could turn out well, sorry.

Status: UNCONFIRMED → RESOLVED
Closed: 3 years ago
Component: Folder and Message Lists → Networking: IMAP
Product: Thunderbird → MailNews Core
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.