Michael, The only way for us to move forward on this, and we do want to get down to the bottom of what causes this, is to reproduce it on this end and run the application under the source debugger.
In order to do so, please send and emptied and compacted set of database files: Address Database Message Database Server-side Database Setup Database User Prefs inside a zip file to us by private mail. We will, in confidence with regard to your data, attempt to reproduce the fetch crash and find the error source. My impression is that PowerMail may be stumbling on an ill- formatted message on the server side that doesn't cause Mail to hiccup, but it could also be an issue with SSL as well (unless you've tried turning that off). Once this is done here, we will communicate back to you via private e-mail. Kind regards, jean michel/ctm qa On Sun, 21 Mar 2010 15:55:57 +0100, MB <[email protected]> wrote: >Tom Bulat said: > >>Either I missed it or else you haven't mentioned any of your settings in >>the mail accounts. >It was mentioned in an offtopic thread. But I should have included those >of course. They are: > > >POP3 >email address: my complete address >Real Name: My name with one umlaut >id: just the part before "@" >incoming: pop.gmail.com >pw: saved in keychain >Use secure connection on a dedicated secure port: 995 (Use port checked) >Leave copies of retrieved messages on the server >Retrieve messages keft on server again: tried both checked and unchecked >Outgoing: authenticate (same as ingoing) >Use secure connection on a dedicated secure port: 465 (Use port checked) > >On gmail.com the Status is: POP is enabled for all mail that has arrived >since 12/19/06 > >However, I renewed the settings for enabling POP also for messages that >have been already downloaded. This is a possible culprit. PM and gmail >obviously don't agree on what messages that have been downloaded because >of PM prematurely disconnecting and the gmail servers may have recorded >that all messages have been offered already and missed that the >connection was dropped. > >This would have been much easier to troubleshoot if PowerMail had >connection error logging and proper duplicate message handling. But this >can be the solution possibly. > >If I can get my remove duplicate script working again after >redownloading all messages and dumping all the old ones that I already >should have, I might be able to solve this in the end. > >PowerMail prematurely dropping connections (long, long standing problem >on many different nets and different Macs) remain a problem that must be >solved or I can't continue to use Powermail. > > > >
