On Tuesday, July 26, 2005 at 2:45:10 AM [GMT -0500], Keith Russell wrote: Firstly, I'm a FastMail user and can confirm that TB! can work well with it. So your problems with it should be reproducible by me if there were problems with FastMail.
> As soon as I started up the new version, I started getting the error > popups (this time for 0588F103.TBB). As before, I was asked whether I > wanted to repair the message base, but whether I pressed Yes or No, > the error message would immediately pop up again. I was able to > eventually get to the repair dialog, but of course, there was no way > to tell which "real" folder 0588F103.TBB belonged to. I selected the > account name and ran the repair for all folders in the account. .... > Eventually, I used Explorer to delete the TBB and TBI files from the > Inbox folder, and that did seem to fix the problem. You could open the properties of one of the problem folders and delete the cache. When TB! caches your mail locally, it creates a tbi (index file for message list) and a tbb file (an actual message base). Hitting the delete cache button deletes those two files. > I am reporting this again because, although I may be the only one > to have experienced this, someone else will certainly encounter > it, and it could very well be a novice user (this is a released > version) who has no clue what to do. Your problem is odd indeed and despite all of TB!'s problems with IMAP, I'm finding it difficult to think the problem is with TB!. For some reason, your cache files are being corrupted. The fact that ThunderBird is OK doesn't necessarily mean that your machine is OK or that some other application is interfering with TB!. I don't know how willing you are to go down that road of trouble shooting. > Someone suggested in a followup in this thrad back in June that > the error message be changed to be more helpful. Not only that, > but I think it is critical that there be some way to dismiss the > error message without it continuing to pop up eternally. Why suppress errors that really shouldn't be triggered? I can't recall the last time I've seen one of those errors. When I did see one, it would pop up once. I delete the cache and it would go away. However, those days are long gone. I'm actually pleased with the cache integrity now. I haven't deleted a TB! cache file in quite a while. I can't recall the last time actually. > (And now to see if I can actually post this followup using TB!) > Postscript: The answer is no, I wasn't able to post using TB. > (I'm using Thunderbird again.) Worse yet, immediately after the > send failed, I started to get the same error all over again, and > again for the same file--which I had deleted earlier and > supposedly had been rebuilt! This is really strange and further makes me wonder what's really happening to your cache files. I'd start thinking more of the system in general and not just TB!. ThunderBird manages, but TB! isn't managing. What's your system like? Hardware description (processor and ram, hard disk space) OS? Version? Antivirus software running and is it proxying your IMAP connection? Any other scanners running that may be scanning cache files as they're written? How is your machine otherwise? All other apps running well? -- -= Curtis =- The Bat! v3.51.10 System Specs: http://specs.aimlink.name -=-=- If it jams, force it. If it breaks, it needed replacing ________________________________________________________ Current beta is 3.51.10 | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html IMPORTANT: To register as a Beta tester, use this link first - http://www.ritlabs.com/en/partners/testers/
