At 10:04 am -0800 22/2/02, Richard Perlman Wrote: >I am new to this list, so this topic may have been addressed - if so, could >someone send me the appropriate postings. > >Background: >I am running OSX 1.1.2 and Entourage X 10.0.1 (1331) > >I use IMAP connecting to the standard UW imapd server running on FreeBSD > >I am subscribed to around 200 mailboxes on the imap server but I only check >for messages in my INBOX folder. I do have Live Sync turned on, only for >the inbox. > >The problem: >At random intervals, around once every day or two, my inbox mail list >display will have missing messages. In other words, where the message >should be, I see the background pattern. Very shortly thereafter, Entourage >will crash. About 1/2 the time a normal rebuild will fix the problem, and >about 1/2 the time I have to do the Advanced Rebuild. Once or twice neither >worked. Fortunately, I have started backing up the Entourage database every >20 minutes in a cronjob. > >I have reported this to MS, and their response is "every database can get >corrupted." But, I have also heard rumors that this is a known problem.
I have not seen any other reports of corruption occurring so frequently as that. I have been running Entourage for X for about 4 months now (handling approx 200 mails per day), and have suffered no corruption whatever. I would suggest that this corruption may be occurring sue to some aspect of the interaction with your imap server. Do you know what sort of server it is? Better still, are you able to see a series of operations that cause the corruption to occur? If so, can you get a tcpflow of the transactions? Some more info like this may assist on tracking the problem down. But, rest assured, corruption occurring more than once a day is NOT how entourage ios meant to be, nor is it how it acts for most people! > >Also, the database seems to grow no matter what I do - even emptying the >message cache does not seem to reduce the db size, which is now at 1.3G. I >have observed that crashes seem to increase in proportion with db size. Emptying the cache does not reduce the database size itself. The database will be left with 'wasted' space in it every time you delete something. However, this is not all bad, since the wasted space is used up with new data as it is added. This way, over a period of time (assuming that you are deleting stuff as you go) the database will probably reach an optimum size, after which the stuff you delete is roughly equal to the stuff you add, and no further growth takes place. If you need to recover the wasted space on your hard disk, you will have to do a 'typical' rebuild to compact the database. This will create a compacted version of the database without the wasted space. You will then have to manually delete the backup copies of the original database that the rebuild process creates AFTER you are happy the new one is OK. -- =Barry Wainwright= <http://www.barryw.net> -- To unsubscribe: <mailto:[EMAIL PROTECTED]> archives: <http://www.mail-archive.com/entourage-talk%40lists.letterrip.com/> old-archive: <http://www.mail-archive.com/entourage-talk%40lists.boingo.com/>
