I am a heavy Pmail IMAP user, connecting to three IMAP sites simultaneously. One site has over 300 IMAP folders with messages dating to 1994. I have been using Pmail since the early Pmail for DOS days, and have the latest version, running on both 64-bit Win7 and 32-bit XP machines (work, home, laptop, not all at the same time).
I have been plagued by Pmail crashing on some IMAP folders.When I try to open certain folders, it opens an empty folder window, and the message count in the folders list blanks out. When I try to close the folder, Pmail hangs, and after several seconds it crashes. As long as I don't try to close the offending folder, I can continue to use Pmail.
This evening I decided to look more closely into the problem. I have fairly definitely determined that it is related to missing or blank message headers. It will happen if the folder contains a message with a missing Date: header, or a blank Subject: header.
I tried the following: Using Mozilla Thunderbird I opened an offending folder and moved a message that had a blank Subject: line to the Inbox. Then I closed Thunderbird and opened the folder in Pmail. The folder now opens normally! I then moved the message with the blank Subject: back to the formerly offending folder. I can now open and close the folder with no problems.
Next I went to the Folder Information dialog for the folder and cleared the header and body caches, closed Pmail, reopened Pmail, and tried to open the folder. It now crashes again!
But wait, it's a bit more complicated than that. I tried again to repeat the same steps, and this time the folder opened correctly after clearing the caches. Then I went and opened the folder in Thunderbird, closed it and opened it in Pmail, and now it crashes again.
I have been having these crashes for the past several versions of Pmail. I also have experienced Pmail crashing on opening an IMAP Inbox. At first I thought it was related to 64-bit Win7, but the problem was not consistent with that. Now finally I have found a consistent pattern.
I hope the developers are reading this and are able to fix this bug.
Thanks,
John Dudeck
Lyon, France
<p>I am a heavy Pmail IMAP user, connecting to three IMAP sites simultaneously. One site has over 300 IMAP folders with messages dating to 1994. I have been using Pmail since the early Pmail for DOS days, and have the latest version, running on both 64-bit Win7 and 32-bit XP machines (work, home, laptop, not all at the same time).
</p><p>I have been plagued by Pmail crashing on some IMAP folders.When I try to open certain folders, it opens an empty folder window, and the message count in the folders list blanks out. When I try to close the folder, Pmail hangs, and after several seconds it crashes. As long as I don't try to close the offending folder, I can continue to use Pmail.
</p><p>This evening I decided to look more closely into the problem. I have fairly definitely determined that it is related to missing or blank message headers. It will happen if the folder contains a message with a missing Date: header, or a blank Subject: header.</p><p>I tried the following: Using Mozilla Thunderbird I opened an offending folder and moved a message that had a blank Subject: line to the Inbox. Then I closed Thunderbird and opened the folder in Pmail. The folder now opens normally! I then moved the message with the blank Subject: back to the formerly offending folder. I can now open and close the folder with no problems.</p><p>Next I went to the Folder Information dialog for the folder and cleared the header and body caches, closed Pmail, reopened Pmail, and tried to open the folder. It now crashes again!</p><p>But wait, it's a bit more complicated than that. I tried again to repeat the same steps, and this time the folder opened correctly after clearing the caches. Then I went and opened the folder in Thunderbird, closed it and opened it in Pmail, and now it crashes again.
</p><p>I have been having these crashes for the past several versions of Pmail. I also have experienced Pmail crashing on opening an IMAP Inbox. At first I thought it was related to 64-bit Win7, but the problem was not consistent with that. Now finally I have found a consistent pattern.</p><p>I hope the developers are reading this and are able to fix this bug.</p><p>Thanks,</p><p>John Dudeck</p><p>Lyon, France
</p>