4.52 Crashes after checking large IMAP folders

IanH — Thu, 26 Aug 2010 16:21:10 GMT

Whenever I try to check an IMAP folder with more that around 100 messages in it, 4.52 crashes. I see the counter in the status bar going through its routine buit after ir gets to some number between 40 and 80, it disappears. Pegasus does not become completely unresponsive, I can click on other folders and they highlight but nothing happens, the other folder, POP or IMAP, doesn't come up. Then the status bar indicates "IMAP: Closing connection to mail.domain.com". That's when the dreaded "This program had a problem..." box comes up.

I've had this problem for weeks, so it's not a new update. Needless-to-say, I've fiddled with the IMAP settings for the accounts pretty extensively but can't seem to hit anything that works.

Can anyone suggest anything?

Running XP, SP 3.

Re: 4.5.1 Buffer Overrun Detected

dom54 — Sat, 24 Oct 2009 15:53:15 GMT

Hi,

I often experiment this king of problem. First the message counter in one of my IMAP folder disappears (normally the iNBOX), then Pegasus states there was an error on the IMAP server and afterwards I get a MS C++ Runtime Library stating that there was a buffer overrr.

I normally restart PMAIL, reconnect to the IMAP server, right click on the INOBX fodler (or the one on which I have the problem) and clear both the header and body cache, then a reindex the folder and the problem is solved.

Sometimes, like today, this solution doesn't work and PMAIL contunies to crash.

In this situation I used to access my IMAP server via a web client move a substantial amount of messages from the INBOX folder to another one and hope that PMAIL is able to reindex the faulting folder. Of course I will prefer to have a "real solution".

Is the use of the mbxmaint.exe and check and reindex the faulting folder teh "real solution"?

Thanks, regards

Domenico

Search Results matching tags 'crash' and 'imap'

4.52 Crashes after checking large IMAP folders

Re: 4.5.1 Buffer Overrun Detected