Mikael Byström ([EMAIL PROTECTED]) on 2006-05-31 04:20 said: >I too was bitten by this identical situation and I finally bit the dust >and got hold of PowerMail Salvage. It cost me $52 in total and it was >worth every penny. > >Watch out though for salvaging just a percent of the messages. Currently >there is no definitive order of messages and dates may be unavailable >for some messages you need, depending on the nature of the damage. > >You may very well end up in a situation with duplicate messages, if you >merge with your backup. If so, you'll need my PowerMail Salvage header >compatible update to the DeleteDups script or similar. Available per request.
I also bought PowerMail Salvage and it helped me out, though it took a while. At first it hung trying to recover messages, but I eventually figured out which messages it was hanging on. So I used it to recover messages since by backup. Maybe I missed some, but its better than nothing. >>However we should probably disable fetching, rather than just displaying >>an alert, when the database size approches 2 GB... > >"Probably"? Skip "probably" and implement in this sound move in an >upcoming incremental update. Hear! Hear! Software should strive never to corrupt a user's data. I'm pretty sure what happened to me is reproducible, and so should be fixed asap. >It's a wonder you guys didn't think about this to begin with. After all >the alert says "getting close to 2GB", not how much closer the current >fetch will get you there and as a user you kind of trust applications to Also I'm pretty sure that the message only appears when launching PowerMail. I run PowerMail for days/weeks (until it eventually crashes) and so there's a problem there! :) -- ____________________________________________________________ Sean McBride, B. Eng [EMAIL PROTECTED] Mac Software Designer Montréal, Québec, Canada
