So here's what I tried so far: Pre-work: deleted pref files and the OS X cache for PM. Reinstalled PowerMail 6.0.3 from a fresh download.
1- I set PM to redownload all messages in my current DB and made a mail filter that deletes all messages before x days - I haven't got any messages since sep 13 2009 on this account - and all attachments before that amount of days. I put the mail filter first of all no further handling, turned off all schedules and started to download 600 messages at a time - which is what the gmail service offers. Result: PM downloads some hundred messages starting with the oldest from 2006 - there are many attachents, which I pointed to a new attachment folder, not my old - and then it quits prematurely. It keeps redownloading also the messages already received before it gives , up again, and again and - you get the picture. I had up to 10 duplicates before I gave up this strategy. 2- I started a completely new and clean user environment. That is a *totally fresh* DB (prework repeated). I set up just the problem gmail account including to redownload all remaining messages. Result: PM downloads nothing, just as before. Nothing at all. Not even one message. As far as PM is concerned there are no new messages. Even in a new fresh user environment. Conclusions: As my other account (this) does work without any problems, there must be something with the problem account that for whatever reason doesn't play with PowerMail. But works with at least one other client: 3- In contrast: I started Mail, wrote in my email address. The account was autoconfigured. I made adjustments in the prefs to leave messages on server. 30 minutes later all my messages inlcuding attachments had been downloaded and is up to date. Zero problems. In addition Mail gave me 300k/s speeds where I usually am glad to see PM doing 2 digit speeds ( I have 8mbit). Comments? I'm not going to use Mail from now on, but this acting up on PowerMails part is getting quite tiresome. For one thing, in this kind of situation, PowerMails lack of logging or details about connections must be considered to be a big, big minus. How can a user be expected to diagnose faulty connections with no tools? And in practical terms for me so far, no support or encouragement from CTM to identify the problem. I think I bugreported this 3 times over the years. Maybe it got lost in the mail. I'd do a bug report again, but I really don't have any new data besides the above that could be of help. MB Technoids: PM 6.0.3 build 4609 sv | OS X 10.5.8 | PowerMac G5 Dual 2.0 | 4GB / 1TB
