On Jan 23, 2006, at 5:02 PM, Andy Fragen wrote: > Agreed. But my experience differs. I've never had an unfixable db > error > with PM and I've been using it since v3
Andy, I also have had PM since v.3 and until Sunday had not encountered a problem that PM could not recover. An interesting side note, and one that really disturbs me, is that just prior to the PM failing to compress with DB errors my account on my OS X server mail server became corrupt and had to be recovered by doing a rebuild on the server. Since I use PM in pop mode for this account, the server only has messages on it for a very short period of time (the build up between checks and logins). This leads me to believe that perhaps the root of this could be a single bad email. As to PowerMail Salvage, I purchased it--given how long it took to run through just 1% of the DB, I didn't want to have run the tool twice since you have to quit to enter the purchase key, and then start the salvage all over again. PMS has been running on my system for over 24 hours, and so far it it reports that his recovered 219,798 messages in 825 folders. The progress bar shows about 10% left to go. Of course until I actually am able to finish the salvage and export the recovered emails, I won't be sure this has worked, but things are looking good. A suggestion to anyone in my shoes. Buy the license key for PMS before running the salvage all the way through once on a large DB. You will just have to start it from scratch again once you get the license key. Second, do the salvage on desktop system and not on a laptop. I have had to drive to and from work with the powerbook open on the passenger seat to keep the salvage running. I would guess that the beefier the machine, the better. Thanks for the feedback from everyone. Robert
