No solution.  The problem is exactly as you describe.  Mercury locks the mailbox when it is being accessed by IMAP, Pegasus Mail locks the mailbox when it has access.  One thing that makes it frustratingly worse is that iDevices do not release the IMAP connection even when the device is turned off which is causing real problems for our people who what to use the Pegasus Mail client while at their desks but rely on IMAP access from a variety of iDevices when traveling. They have no choice but to ignore the lock warning of Pegasus Mail.  I think I have had to repair folder corruption only once because of this.

The questions was asked regarding why it is a problem in v4.8 but wasn't in v4.74 and the response was that v4.74 must have been broken because simultaneous mailbox access can cause corruption regardless of the type of connections.  For me it would be helpful if a connection attempt by Pegasus Mail on an IMAP locked mailbox generated an option to disconnect and block any IMAP connections during the session.  This would work because my folks already know to call in and have someone shut down their Pegasus Mail when IMAP attempts hit a locked mailbox. 

FWIW, Mercury handles all of our mail processing and spam filtering so there is no advantage for a user to leave Pegasus Mail running.

I have a user using a Blackberry to connect via IMAP.  When running V4.74 he would receive notice of new messages on his phone throughout the day even with the mailbox open by Pegasus Mail but on v4.8 he must shutdown Pegasus Mail in order to receive messages on his phone.  Did something change in v4.8 to affect this behavior?

--
Brian Fluet

[quote user="Brian Fluet"]I have a user using a Blackberry to connect via IMAP.  When running V4.74 he would receive notice of new messages on his phone throughout the day even with the mailbox open by Pegasus Mail but on v4.8 he must shutdown Pegasus Mail in order to receive messages on his phone.  Did something change in v4.8 to affect this behavior?

--
Brian Fluet[/quote]

Have you a session log that shows what's happening?

The session log shows a successful connection and closes with a messaged to the effect that the mailbox is in use by another process.

My iDevice users have reported the problem as well.  Based on the behavior, it appears that IMAP mailbox access is blocked when the Pegasus Mail lock file exists.

I checked this with David and he says that it's not possible to access a mailbox via IMAP when a local copy of Pegasus Mail has it locked. The two processes simply cannot access the same data in a coordinated manner. Multiple access via IMAP is OK though, with the exception of the EXPUNGE command. The new MailStore in v5 will however provide a way to do that.

Hi Rolf,

having the same problem but didn't find that thread - wrong searchwords. :-(

Have a look at http://community.pmail.com/forums/thread/44954.aspx

> I checked this with David and he says that it's not possible to access a mailbox via IMAP when a local copy of Pegasus Mail has it locked.
> The two processes simply cannot access the same data in a coordinated manner.

It worked for a long time (my last version was V4.73, Brian had V4.74) and obviously without any problems. MAILBOXM.LCK and MAILBOXP.LCK were created with older Mercury and same Pegasus too, but neither Pegasus or Mercury didn't react to the existence of the other file. Why change that behaviour? And I wonder why my unchanged Pegasus does now after upgrading Mercury to V4.8.

And my personal mailbox is a very special one (but only mine - the other users don't have it that way). I divided it via PMAIL.INI into a NewMailDiretory (New mailbox location) and Mailboxdirectory ((Working) home mailbox location), so IMAP only has access to new mails (OK - and a trash and sent folder :-) and not the folders of the mailbox and folders accessed with Pegasus. This is a historical issue (caused by Novell Netware) but still has some advantages.

Regards

   Olaf

The way it works in v4.80 is apparently the way it was intended though, for data integrity reasons. If the new mailstore will be able to provide simultaneous access via IMAP and Pegasus with preserved security it should be allowed in v5.

Hallo Rolf,

so - my users have the choice:

• use Pegasus, which blocks any IMAP-Access to their mailbox
• use their mobilityhardware with android, iOS or what ever and any IMAP-mailclient when ever they need access and therefore swap to Outlook, Thunderbird or so, because this blocks Pegasus.
  

What do you think they will do in modern times? They won't accept any loss of communication capabilities!

As long as there is no new mailboxformat with PM5 and Mercury x.x allowing shared access to the mailbox without any risk on dataintegrity, I would prefer to have the old behaviour as a choice in Mercury. Maybe with a big, fat hint on the risk, that I have to accept prior to configuring it.

In my personal special case there is no risk due to splitting in New Mailbox Location and Home Mailbox Location and thats what I simply can do for my users.

Regards

    Olaf

I realize that this is an old thread but I just upgraded from 4.73 to 4.80 and encountered this issue. We tended to keep Pegasus open all the time because it takes time to open and because its spam processing kept a lot of spam off of our mobile clients. But with 4.80 that locks out the mobile clients (IOS). On the plus side, everything loads faster and better in IOS mail, but if you forget and leave the Pegasus client open, you have no mobile mail capability at all until you get back to Pegasus which could be hours or days. Has anybody ever found a solution to this problem. I'm considering just re-installing 4.73 or 4.74, but I'm hoping for a better idea.

 Thanks,

Barry