Without some idea of exactly what Exchange is doing that's causing the problems, I can't even offer a diagnosis. I don't have access to an Exchange 2010 server, either, so there's no way I can look into this myself.

Pegasus Mail's IMAP support is fairly basic - it doesn't do anything very complicated, so it's hard to imagine what Exchange could be doing that could cause so many issues... That said, IMAP is incredibly dense, and there's bound to be plenty of things I've never anticipated.

If someone can get session logs showing the command/response sequences leading to problems like this, I'd be happy to look into it, but without pretty clear illustrations of what's going on, there's absolutely nothing I can do.

Cheers!

-- David --

My university has just switched us to MS Exchange, and a colleague and I who insist on using Pegasus rather than Outlook have found that our IMAP service has degraded terribly.  We get the error message "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 completed." frequently and almost at random, though noticeably often when dealing with subfolders.  The result is that copies of outgoing emails get lost, PMail frequently crashes (not always), and mails which had been dealt with and moved or deleted turn up again in the inbox after a restart - this is IMAP, after all - wasting a lot of time.  Today's response from the senior sys admin is as follows:

• I'm afraid we haven't any good news here.
• We moved your email account to a new email service, but it can't provide the same quality of experience in Pegasus that you have been used to. We've spoken to our supplier, Microsoft, but they view IMAP as a legacy access protocol and have no plans to fix the issues we identified in their product. This hasn't changed since we first highlighted these issues to them more than 12 months ago. <snip>
  
• We can offer you our help to move towards one of our recommended and supported access methods, such as Outlook 2007 on Windows or Outlook Web App via any browser. I'm sure there will be differences between Pegasus Mail and Outlook, but the option is there. We stopped supporting Pegasus Mail in 2006 and, 5 years later, we'd encourage you to make the switch.
• The final decision about which product to use is in your hands, and if you'd prefer to stay with Pegasus this is no problem. But I'm afraid we have no means to improve that experience for you

My questions to the forum are as follows:

Have any of you got Pegasus to play nicely with MS Exchange 2010 on IMAP?

If so, what performance settings do you use in Pegasus?

Is there anything we can suggest to the support people that they could do with MS Exchange (other than bin it, obviously)?

Will the next major PMail release work better with MS Exchange?

Thanks

David

No response from anyone yet.  Maybe my msg was too wordy.  I would really hate to be forced away from Pegasus after so many years, so help would be welcome. To repeat the questions:

• Have any of you got Pegasus to play nicely with MS Exchange 2010 on IMAP?
• If so, what performance settings do you use in Pegasus?
• Is there anything we can suggest to the support people that they could do with MS Exchange (other than bin it, obviously)?
• Will the next major PMail release work better with MS Exchange?

• Is the DavMail gateway a practical solution? - a colleague thinks he has got IMAP on Exchange 2010 to work OK with Pegasus using this gateway.

Thanks.

David