Thunderbird is stuck at “Downloading message 1 of 140”

The status bar remains at “Downloading message 1 of 140”. New customer emails do not appear, or retrieval repeatedly starts at the same point. The label describes a stalled operation, not its cause. Mozilla's receiving guide begins with comparisons of provider access, account configuration and actual message availability. Q1

Identify where the mail is stored

IMAP, POP and local folders have different storage and synchronisation paths. Before moving a message or recreating an account, establish which data exists only locally. A complete profile backup made while Thunderbird is closed preserves the baseline for investigation. Q2

Locate the stalled stage

1. Observe duration and scope. Record whether the count changes, whether only one account is affected and whether the interface remains responsive. A large transfer making progress is different from repeated failure at an apparently unchanged point.
2. Compare webmail. Check whether new messages exist at the provider and whether the mailbox itself is accessible. Initially compare only the subject, time and size of a harmless message. Do not open suspicious attachments as a download test.
3. Identify account type and phase. Does the connection complete authentication? Are folder lists visible? Does it always stop at one message or only at large messages? These distinctions separate authentication, transfer and subsequent processing.
4. Check local storage. Inspect free space at the actual profile location and any write-error messages. Record whether the profile lives on synchronised or remote storage. Do not move an active mail store while retrieval is running.
5. Choose a limited comparison. After backing up, a separate test profile with appropriate account access can help. For POP, first establish whether the test would remove messages from the server. Blindly recreating an account can change the evidence and jeopardise data.

Follow the observed branch

If webmail itself fails, begin with the provider. If retrieval works in a separate profile, investigate local configuration and storage access. If one specific message consistently triggers the stall, initially give support its identifier and technical characteristics rather than automatically disclosing confidential contents. An index repair should follow evidence that points to indexing, not merely an unchanged progress bar.

For handoff, record Thunderbird version, account type, onset, profile storage arrangement and exact status text. The original candidate thread was not fully readable during the current retrieval, so this guide does not claim a confirmed solution from that discussion. Q3

Frequently asked questions

Should I delete the first email?

Not without positive identification and a backup. The displayed number does not establish that a particular message is defective.

Should I compact every folder immediately?

That does not replace distinguishing a provider, transfer or storage problem. Preserve the data and the specific finding first.

Describe your case