<p>I enabled logging and the problem went away. It comes back often.</p><p>I found that I get the error sometimes when I try to open a message in a folder. I can correct this problem by closing and then opening the folder. </p><style></style>

<p class="MsoNormal"><span lang="EN-US">For several months I have had an annoying problem with Pegasus Mail that appeared out of the blue, and I have not been able to figure  out the cause. </span></p><p class="MsoNormal">After opening Pegasus, it works OK for about 10 minutes. After that time, when I click a new email, <span style="font-size: 10pt;">I get an error message saying: "</span><span style="font-size: 10pt;">The IMAP server that manages this mailbox or folder has reported an error during the operation you have attempted to perform. The operation cannot be performed."</span></p><p class="MsoNormal">Each time this error message box appears, I need to click the OK for 5 times, after that the email opens saying:  "This message contains binary or non-textual data that cannot be previewed within Pegasus Mail.</p><p class="MsoNormal"><span style="font-size: 10pt;"> Filename:   ÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌ </span><span style="font-size: 10pt;">You can work with this file in the message reader's 'Attachments' page."</span></p><p class="MsoNormal"> </p><p class="MsoNormal">After  that I need to close the NewMail folder and and press Ctrl+W (read new mail). Then I can continue working with the emails, again about 10 minutes, and the error mesage appears again.</p><p class="MsoNormal">After re-opening the  NewMail folder, some of messages that I have previously deleted before the previous error message appear in the list with the message-title text dimly highlighted and over-striked.</p><p class="MsoNormal"> </p><p class="MsoNormal"><span style="font-size: 10pt;">Our IT department at the University claim that they have not made any changes to their mail servers at the time my problems started. Any ideas how to fix this would be MUCH appreciated.</span></p><p class="MsoNormal"> </p><p class="MsoNormal"> </p><p class="MsoNormal"> </p><p class="MsoNormal"> </p><p class="MsoNormal"> </p><p class="MsoNormal"> </p><p class="MsoNormal"> </p>

<p>I experience exactly the same symptoms with IMAP on a MS Exchange server at my university. Only difference is that it usually works OK for longer than 10 minutes at a time. I also have an alternative problem, which is that PMail goes dim and locks up for half a minute or so, though it usually works OK without further action when it comes back to life. I too would appreciate advice on what to look for. Thanks.</p><p>David </p>

<p>I can't speak to the IMAP issue but I do know that many folks experience what appears to be a hang in Pegasus Mail v4.70 whenever it is sending, receiving, or checking a server.  It clears up after a number of seconds.  I wonder if this is what you are experiencing although the 'half a minute' you mention is a long time unless a number of servers or mailboxes are being checked each time. </p><p>My experience is that is is worse on slower machines and from what I have heard it is not prevalent enough for David or the beta testers to get a handle on exactly what is causing it. </p>

<p>Have you used session logs to look at the problem?</p><p>If not go to Tools | Internet options | General and check create session logs.</p><p>If you haven't used it in the past look at the associated help files first. </p>

<div>OK, I turned on the internet session log. This seem to create 2 files under PMAIL/MAIL/ADMIN/TCPLogs: TCP-XXXXXX-YYYY-X.imap. It's tail is shown below: </div><div> </div><div> </div><div>1:33:39.541: >> * 72 FETCH (FLAGS (\Seen \Answered))<cr><lf></div><div>11:33:39.542: >> A28 OK STORE completed.<cr><lf></div><div>11:40:51.284: << A29 UID FETCH 154980 FLAGS<cr><lf></div><div>11:40:51.285: [!] OpenSSL reported a write error - error queue follows:</div><div>11:40:51.285: [!] ---------------------------------------------------------------------------:</div><div>11:40:51.285: [!] ---------------------------------------------------------------------------:</div><div>11:41:07.460: << A30 UID FETCH 154977 FLAGS<cr><lf></div><div>11:41:07.460: [!] OpenSSL reported a write error - error queue follows:</div><div>11:41:07.461: [!] ---------------------------------------------------------------------------:</div><div>11:41:07.461: [!] error:1409F07F:SSL routines:SSL3_WRITE_PENDING:bad write retry</div><div>11:41:07.461: [!] ---------------------------------------------------------------------------:</div><div>11:41:08.786: << A31 UID FETCH 154977 (FLAGS UID RFC822.SIZE BODY.PEEK[])<cr><lf></div><div>11:41:08.787: [!] OpenSSL reported a write error - error queue follows:</div><div>11:41:08.787: [!] ---------------------------------------------------------------------------:</div><div>11:41:08.787: [!] error:1409F07F:SSL routines:SSL3_WRITE_PENDING:bad write retry</div><div>11:41:08.787: [!] ---------------------------------------------------------------------------:</div><div>11:41:09.348: << A32 UID FETCH 154977 (FLAGS UID RFC822.SIZE BODY.PEEK[])<cr><lf></div><div>11:41:09.349: [!] OpenSSL reported a write error - error queue follows:</div><div>11:41:09.349: [!] ---------------------------------------------------------------------------:</div><div>11:41:09.349: [!] error:1409F07F:SSL routines:SSL3_WRITE_PENDING:bad write retry</div><div>11:41:09.349: [!] ---------------------------------------------------------------------------:</div><div>11:41:09.837: << A33 UID FETCH 154977 (FLAGS UID RFC822.SIZE BODY.PEEK[])<cr><lf></div><div>11:41:09.837: [!] OpenSSL reported a write error - error queue follows:</div><div>11:41:09.837: [!] ---------------------------------------------------------------------------:</div><div>11:41:09.838: [!] error:1409F07F:SSL routines:SSL3_WRITE_PENDING:bad write retry</div><div>11:41:09.838: [!] ---------------------------------------------------------------------------:</div><div>11:41:10.365: << A34 UID FETCH 154977 (FLAGS UID RFC822.SIZE BODY.PEEK[])<cr><lf></div><div>11:41:10.366: [!] OpenSSL reported a write error - error queue follows:</div><div>11:41:10.366: [!] ---------------------------------------------------------------------------:</div><div>11:41:10.366: [!] error:1409F07F:SSL routines:SSL3_WRITE_PENDING:bad write retry</div><div>11:41:10.366: [!] ---------------------------------------------------------------------------:</div><div>11:42:38.598: << A35 CLOSE<cr><lf></div><div>11:42:38.599: [!] OpenSSL reported a write error - error queue follows:</div><div>11:42:38.599: [!] ---------------------------------------------------------------------------:</div><div>11:42:38.599: [!] error:1409F07F:SSL routines:SSL3_WRITE_PENDING:bad write retry</div><div>11:42:38.599: [!] ---------------------------------------------------------------------------:</div><div>11:42:38.600: << A36 LOGOUT<cr><lf></div><div>11:42:38.600: [!] OpenSSL reported a write error - error queue follows:</div><div>11:42:38.600: [!] ---------------------------------------------------------------------------:</div><div>11:42:38.601: [!] error:1409F07F:SSL routines:SSL3_WRITE_PENDING:bad write retry</div><div>11:42:38.601: [!] ---------------------------------------------------------------------------:</div><div>11:42:38.601: [!] Warning: SSL connection improperly closed by remote host.</div><div>11:42:38.602: --- Connection closed normally at 15 Jun 2015, 11:42:38.602. ---</div><div>11:42:38.602: </div><div> </div><div>It also created a file:  <span style="font-size: 13.3333330154419px;">TCP-XXXXXX-YYYY-X.smtp, it's tail is shown below:</span></div><div> </div><div><div>1:56:32.400: << </body><cr><lf></div><div>11:56:32.400: << </html><cr><lf></div><div>11:56:32.400: << <cr><lf></div><div>11:56:32.401: << --Alt-Boundary-29335.255569308--<cr><lf></div><div>11:56:32.401: << <cr><lf></div><div>11:56:32.401: << --Message-Boundary-29643--<cr><lf></div><div>11:56:32.401: << .<cr><lf></div><div>11:56:32.997: >> 250 2.6.0 <557E933F.29466.F3BAD9C@olli.raitakari.utu.fi> [InternalId=25601045] Queued mail for delivery<cr><lf></div><div>11:56:33.000: << QUIT<cr><lf></div><div>11:56:33.001: >> 221 2.0.0 Service closing transmission channel<cr><lf></div><div>11:56:33.002: [!] Warning: SSL connection improperly closed by remote host.</div><div> </div><div> </div><div>Any suggestions what is causing the problem?</div><div> </div><div>Olli</div><div> </div></div><div> </div>

I have had exactly the same problem using Pegasus Mail (version 4.63) with Windows 7 and 8.1, with the IMAP server of Gmail.

<p>An implementation of SSL currently used by many mail servers is incompatible with versions of Pegasus Mail prior to v4.70.  This incompatibility shows itself when the SSL of your email server gets upgraded.  This means your Pegasus Mail v4.63 and prior could be working one day and not the next.</p><p>A setting to look at that is new to v4.70 is the "Use only SSLv3.." setting located in the Security tab of each POP3 and SMTP host configuration and each IMAP profile.  You will likely need this setting to be disabled but if there are still problems then test with it enabled. </p>

I'm using version v4.70. I selected "only use SSLv3", but this did not work. I got an error saying: The IMAP server that manages this mailbox or folder has reported an error during the operation you have attempted to perform.<div><span style="font-size: 10pt;">The operation cannot be completed.</span></div>

<p>I think that the error message is of a generic nature and doesn't point to the actual problem.</p><p>The log file is more significant and seems to point to problems with the SSL routines. To me it looks like an issue for the developer.  </p>

[quote user="Olli"]I'm using version v4.70. I selected "only use SSLv3", but this did not work. I got an error saying: The IMAP server that manages this mailbox or folder has reported an error during the operation you have attempted to perform.<div><span style="font-size: 10pt;">The operation cannot be completed.</span></div><p>[/quote]</p><p>If you have tested with the "only use SSLv3" option both enabled and disabled then we have ruled out the known SSL compatibility issue.  There is something else going on with SSL which Caisson alludes to.  Unfortunately I don't have any additional advice. </p>

I'm afraid Pmail has never been too strong on IMAP. I've been using Thunderbird for over a year now (due to the fact that Windows XP support stopped and I switched to Linux Mint) and IMAP works fine for me now. Other than that, Pmail has always served me greatly!