Marlyse, thanks for your suggestions. Marlyse Comte said: >you so sure it is not your harddrive etc. - well SOMETHING is different >then what the general user comes accross, as it is not a general problem >you are describing.
I suppose you meant that this is not a *known* problem? While I regard you and other individuals on this list as Powermail gurus, I wouldn't ask or expect from any of you to know the details about any conceivable problem, unless you read the source code for both OS X and PM at bedtime. I design databases. I can assure you that it is a humbling experience to see that certain users can find holes in your design that you didn't even know existed. From this I learnt that users finding these holes are not nitwits, but great sources of wisdom that can improve my product. So while it's most likely too late to fix v. 3.1.3, I'm pretty sure, if even with intuition, that I've stumbled on a bug. If it have not been fixed, inadvertently or with intent, chances are that it remains in the code of v4. Is it not? To get back to my specific problem, I must say that these facts should *never* come together in a reasonably bug free database product: €Powermail is seemingly finding my database healthy as verification goes through without remarks. €Importing mail, changing the label of these and moving these to a new folder is causes "Database error 7". €A low level rebuild seemingly works out well and verification is again successful. €Messages disappear from one folder, first the 2200 imported messages, then the newly collected and also every outgoing message moved there by the filter function. A veritable "black hole". €A new low level rebuild doesn't bring back any messages at all. € Disc checks reports that the disc is healthy and no other apps are experiencing problems. >It could be many different things, configuration, >export path, export options, older software version... if you can nail >that down you are a big step closer. I think that this will be hard to nail down on my own, but I'll try some other options for export/import. Maybe I need to "wash" the data through another app prior to importing to PM. Or maybe not. I need to backup a lot of folders anyway, so I'll see what I can do. I do think that's even of there are errors in the imported content, Powermail shoud be able to either fix or at least state a warning. Normally, content shouldn't affect operation very much and if it can, import procedure should filter out characters that can cause havoc. >everybody is trying to help you, but don't expect us to know the answer. I'm not, but I was hoping that this problem could be taken seriously and not as some kind of freak occurrence. I'm very thankful for the experience you share of course. Keep in mind, that I followed a path laid out by CTM. Of course I'm surprised that some of my experienced problems would be totally unheard of. Granted, I'm using PM 3.1.3 under a OS version that wasn't known when it was developed, but someone from CTM (I lost the name with data) said it could be used under OS X 10.2.5, which is why I tried. I'd like to believe this person know what he/she was talking about. Nevertheless I may try the v4.1 demo, but I'm not sure what a successful import without a fully functioning app can tell me as collecting mail post registering may be needed to trigger the bug that may reenter the loss of mail messages. I'd constantly be worrying that I'm losing messages. I'd need a log function that keeps track of changes to folders. Are there scripts for PM that can perform this or are there perhaps beta versions with debug functionality left in that I can use? CTM?
