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.

ค้นหาฝ่ายสนับสนุน

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.

เรียนรู้เพิ่มเติม

Always "building summary file for inbox" for 10~20 minutes at a time? Profile on NAS drive. [win8]

  • 8 การตอบกลับ
  • 4 คนมีปัญหานี้
  • 2 ครั้งที่ดู
  • ตอบกลับล่าสุดโดย Matt

more options

As it says, sometime a couple of times a day, messages are stored on server. Only thing i can think of is that if server goes to sleep then they wouldn't be immediately accessible, but then the server wakes up. And even if you shut thunderbird down, it still comes back up and spends 10+min "building summary file for inbox".

As it says, sometime a couple of times a day, messages are stored on server. Only thing i can think of is that if server goes to sleep then they wouldn't be immediately accessible, but then the server wakes up. And even if you shut thunderbird down, it still comes back up and spends 10+min "building summary file for inbox".

เปลี่ยนแปลงโดย Wayne Mery เมื่อ

การตอบกลับทั้งหมด (8)

more options

Is your Thunderbird profile on local disk, or on a file share?

more options

Program runs on my local computer, profile is on local computer, mail folder storage is on server.

more options

Sorry, mail folder storage is on NAS drive

more options

Anybody have any ideas? I have deleted 1000's of emails, now down to just over 5 minutes building file. This morning I checked my emails no problems, had another look 30 minutes later and "building summary file", so I timed it. 5 minutes is a PITA and a long time waiting.

more options

HELP! I'm having same problem since TBird automatically updated software today to vers 52. Every time I open TBird I now get an error message: "Unable to open the summary file for Inbox. Perhaps there was an error on disk, or the full path is too long." and then TBird spends several minutes re-synching my company IMAP email inbox of 8000+ emails. Never ever had an issue last 3 years before the TBird 52 update, only synched the most recent mail in IMAP like a good ol server should. Thankfully I'm on highspeed broadband at home office, but I can't be doing this on an airplane wifi or tethered to my phone.

more options

I wonder when mine updated to V52 and whether this was pivotal to my problems? Is it possible to roll back to an earlier version?

more options

ASchaidler said

HELP! I'm having same problem since TBird automatically updated software today to vers 52. Every time I open TBird I now get an error message: "Unable to open the summary file for Inbox. Perhaps there was an error on disk, or the full path is too long." and then TBird spends several minutes re-synching my company IMAP email inbox of 8000+ emails. Never ever had an issue last 3 years before the TBird 52 update, only synched the most recent mail in IMAP like a good ol server should. Thankfully I'm on highspeed broadband at home office, but I can't be doing this on an airplane wifi or tethered to my phone.

@ASchaidler If the above information does not resolve your issue, please consider creating a new thread containing the specific details of your issue.

Doing so will allow the Mozilla volunteers to give you solutions that are more helpful to you. This may help them to solve your problem faster and more efficiently.

Please, feel free to post the link to your thread on this thread for volunteers interested in assisting you.

Thank you.

more options

100td said

I wonder when mine updated to V52 and whether this was pivotal to my problems? Is it possible to roll back to an earlier version?

Pivotal to your problem is storing your mail on a NAS device. You move from a hard disk where access is measured in the GB per second to a NAS device where access is an order of magnitude slower. So of course actions which result in the reading of the entire message store are also going to be orders of magnitude slower.