I can't help thinking that maybe PM should be able to deal with such corrupted HTML messages more gracefully than this. Victor alone would seem to have lost 24 hours or more of time to this problem. Certain things need to be acknowledged I think:
1. Whatever our feelings about them, we all receive HTML messages. 2. HTML messages can become corrupted. 3. By the very nature of email, many people will have mail databases dating back several years. 4. If one corrupt email can throw PowerMail completely for a loop, then there *must* be a better way of assisting the user to locate that problem message than simply relying on them to sift through 30... 50... 100,000 messages trying to find the one. Assuming that they can get PM to open in order to do it of course. Even if it's just a crash log entry recording where the offending message is in the database, that would be some help. Rick -- G5 2GHz x2 :: 2GB RAM :: 10.4.5 :: PM 5.2.3 :: 3 pane mode Shark Attack: A Design Studio <www.sharkattack.co.uk> -- Original message: Received from A-NO-NE Music on 20/3/06 at 16:55 >Victor Orly / 2006/03/20 / 11:16 AM wrote: > >>Now, three time over the last two days, it wants to >>rebuild the sort inces - which takes 12+ HOURS. When it is >>done, it just closes right away and wants to rebuild >>again. >> >>What is going on? > >I had this a while ago, and the culprit was a corrupted HTML message >from years back. Took me a while to find that one. I ended up deleting >3-4 suspicious ones. After that, all has been well.
