Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was archived. Please ask a new question if you need help.

In Box repair

  • 1 reply
  • 1 has this problem
  • 9 views
  • Last reply by jon_malins

jon_malins
jon_malins
more options

My Thunderbird In-Box is corrupted so I am running a Repair. The BT IMAP Server randomly fails on the FETCH command and doesn't reply with all requested.

After this my InBox is littered with blank messages all with the same timestamp. InBox has 6000 messages (I know!!)

Is there a way to repair just the failed? Is there a way to get the Repair to retry on failure? Maybe reduce the size of the Block on a Fetch? Any other solutions, or just wait for BT to fix their server (I have messaged them)?

Thanks Jon

My Thunderbird In-Box is corrupted so I am running a Repair. The BT IMAP Server randomly fails on the FETCH command and doesn't reply with all requested. After this my InBox is littered with blank messages all with the same timestamp. InBox has 6000 messages (I know!!) Is there a way to repair just the failed? Is there a way to get the Repair to retry on failure? Maybe reduce the size of the Block on a Fetch? Any other solutions, or just wait for BT to fix their server (I have messaged them)? Thanks Jon

All Replies (1)

jon_malins
jon_malins Question owner
more options

This is the error message I get. BT seem to think it is a client problem and not a server problem.

I have tried setting the Maximum No of Sever Connections to cache to 1. This doesn't seem to have changed anything.

Jon