User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.1) Gecko/20061010 Firefox/2.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.1) Gecko/20061010 Firefox/2.0 using SeaMonkey 1.0.7 Mozilla/5.0 (Windows; U; Windows NT 5.1; de-AT; rv:22.214.171.124) Gecko/20061211 SeaMonkey/1.0.7 mail client have 9 accounts some mail folders conatin more than 1000 mails each time i start sea monkey and for examlple want to search in folder "sent mail" of one account the client builds the summary file new. this takes time for 1800 mails.... i clicked on every folder to make a summary file at least once for every folder. does not help. i used netscape 7.1 german before for my emails and the sea monkey installer automatically imported / got back to my old emails they are still in the netscape profile folder and netscape works fine with them Reproducible: Always Steps to Reproduce: 1. starting seamonkey 4email clinet with many accounts and many mails 2. want to look in one folder with many emaisl (e.g. 1800) 3. client makes a summary file first (see status line below, takes some minutes) for the same folder after some hours he makes again summary file anda again ad agein. waiting for this is ennoing... Actual Results: read text above Expected Results: read text above building up a summary file once is ok and then do not forget this summary< for the folder
I've the same problem (rebuild of summaries over and over again, taking minutes). For me, rebuild occurs after the Microsoft "ntbackup" backuped my Thunderbird profile directory (to some samba network drive). Thunderbird version 126.96.36.199 (20070221)
SeaMonkey v1.0.x is not supported anymore. Thunderbird v1.5.x is not supported anymore. Can you reproduce with SeaMonkey v1.1.9 ? (or Thunderbird v188.8.131.52 ?)
Summary: mail client makes summary files over and aover again → mail client makes summary files over and over again
Version: unspecified → SeaMonkey 1.0 Branch
Assignee: general → mail
Component: General → MailNews: Main Mail Window
QA Contact: general
At my side, the bug disappeared already long ago. (Sorry for late answer.) So, 184.108.40.206 and (.14) are fine.
WFM according tocomment #3
Status: UNCONFIRMED → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.