Error condition confirmed as follows:

For unknown reason where Pegasus detects an error on sending then the 

file IMC-3E9/FOLDERS.PFC is changed to contain one line (D "/").

This IMAP connection can no longer be accessed until this file

is deleted.

Hope someone on the development team can take this from here.

Ever since I purchased a new laptop with Windows10 I have had the following problem which is reoccurring. Frequency varies between a couple of days and 1 1/2 months.

On deleting a message from the server inbox an error popup appears. Further attempts to access the server are completely ignored. Status line 'Press <F1> for help' does not change and nothing is written to the TCP logs.

Usually Windows restart and replace IMAP.PM will set everything straight, HOWEVER sometimes Tools>IMAP profiles...>"name">Connect results is "Name" showing up in the tree and no attempt to connect to the server. Also no error appears. 'Press <F1> for help' does not change and no TCP log is created. Only fix I have found is Uninstall/Install Pegasus and restore all folders and config files.

You might also note that I have 26 years in IT and have been a Pegasus user for 30, so I kind of know what I am doing. Could you suggest some place on disk or in the registry that I might look for something that could cause this problem?

Which service are you connected to? Is this a company's private mail server, or is it a public e.g. gmail/outlook(hotmail) etc., account? If it is a private mail server make sure there are no local connections being made to the account at the same time you are accessing it via IMAP. Finally, what is the text of the error message?

I have two IMAP servers both have had this problem but not together. This morning the UofA connection failed after moving a file from it to a local folder but the Hotmail connection continued to work properly

1> Hotmail: imap-mail.outlook.com port 993

2> UofA: outlook.office365.com port 993

Just had the problem again this morning. Found nothing in the registry or event viewer. Since I can't create a TCP log when the situation exists, I am totally stumped.

What is the text of the error message popup that you mentioned in your original post? Set Pegasus Mail's system message reporting level to 5: Tools > Options > User Interface > Reporting/logging.

Refer to page 167 of the manual for more information on capturing TCP/IP logs. The verbose logging level (level 5) should hopefully shed some light on what is happening.

I will try level 5 and see if anything else shows up. Thanks for the pointer. Problem happened again this morning after timeout(?). Popup is the imap generic 'Server has reported a problem' but at error level 3 log does not say anything. Remember though that the proven fix is to uninstall then install pegasus.

If the logs do not help, contact your mail server provider's support. They will be able to let you know the exact error the IMAP server logged. We can't do much until we know the cause. Uninstalling and reinstalling is fine, but may not fix the problem depending on what the error is.

When the error occurs the TCP log does not help because there was no attempt to make a connection in the first place. For the same reason calling the provider would not help because since there was no connection attempt there is nothing for them to look at. There is some previous error that Pegasus stored somewhere that on retrieval where the code says "n=getErrorCondition();if (n == failing condition) return". Do you know where I can get a copy of the source so I can see where this error condition is stored? Or can someone take a look for me?

I don't have an answer but if I were troubleshoothing this I would use Han's Guide to Filenames and Extensions to identify all IMAP related files and then take them out of the picture, maybe one at a time, to see if one of them is causing the error.  Your experience indicates that you have probably already tried this but I'm throwing it out there for lack of any other suggestions.

In addition to Brian's suggestion, if a connection request was not made, might it have been blocked? Have you checked the logs of your security software to make sure that nothing is being blocked - possibly via behavioural analysis. Some security software automatically blocks without notification so you may not be aware the action has been taken.

FINALLY!!!!

Have not posted for a while because I worked out a work around. Wrote a shell script script that copies out files from MAIL directory with local content,, untars a backup from after a fresh install

and then copies the files back. However problem is back with a vengence and fix did not work.

HOWEVER

TCP log finally came up with something that makes sense. First turnied on logging, connecting to IMAP server, and got the inbox list, All OK.

Moving position to third message and clicking delete got an error and added the following to the log

16:34:23.135: << A4 UID FETCH 28441 (FLAGS UID RFC822.SIZE BODY.PEEK[])<cr><lf>
16:34:23.347: >> * 85 FETCH (FLAGS (\Seen) UID 28441 RFC822.SIZE 74360 BODY[] {22005}<cr><lf>
16:34:23.356: >> )<cr><lf>
16:34:23.357: >> A4 OK FETCH completed.<cr><lf>
16:35:10.561: << A5 UID FETCH 28352 (FLAGS UID RFC822.SIZE BODY.PEEK[])<cr><lf>
16:35:20.596: 26: SSL_read returned zero (socket was closed)

I had previously deleted and moved a number of messages. Only difference might be size related.

Narrowed down to a problem with the IMC-FFF directory for this IMAP.. Deleting it forces pegasus to recreate it and all is well. I will post when I nail it down further