[quote user="kaspencer"]And it is very inconvenient because it takes an age to relocate the folders.[/quote]

Please explain what you mean here.  When is this happening and how long does it take?

Hello ...

I have noticed, since I upgraded to Pegasus Mail version 4.63, that I am quite frequently getting the error "Mailbox is locked" on starting Pegasus Mail. I have used Pegasus Mail since about 1996 or 97, and have very ocasionally seen that error when there has been no identifiable cause, but that incidence has been very low. Of course, sometimes it has been genuine owing to a mailbox having been left open on a different workstation.

It is a bit inconvenient having to wait for the relocation of mail folders (when one has so many!) nearly everytime I open Pegasus Mail.

For background: For many years I have used a Windows Server 2003 R2 for network server storage of mail files, and nothing has changed on the server around the period of upgrade of Pegasus versions. (In the 1990s I used NT Server, and then Windows 2000 Advanced Server.) The new issue in version 4.63 seems to ocurr on both 64- and 32- bit Windows, and on XP, and Vista and Server 2003 R2.

Is this a little buggette in version 4.63; are others experiencing the same issue?

Regards & thanks

Kenneth Spencer (a grateful user for so long)

.

Our small business has10 users with Pegasus Mail and the mailboxes on a Server 2003 box.  We also use Mercury.  I am glad to report no mailbox lock issues on either our WinXP or Win7 workstations. 

There has been some recent discussion about Mercury IMAP locks causing mailbox lock issues.  The discussion has been around IMAP access.  Mercury sets a mailbox lock during IMAP access which doesn't get released promptly upon disconnect or an IMAP connection by a smart phone that never disconnects.

You can check the mailbox folder of a locked mailbox to see what lock is in place.  Existence of a MAILBOXP.LCK file indicates a Pegasus lock, a MAILBOXM.LCK file indicates a Mercury lock.  

If you aren't using Mercury then assume Pegasus Mail is failing to shut down correctly.  Perhaps windows is being shut down while Pegasus Mail is running causing disconnection to the mailbox folder before Pegasus can update its configuration files and release the lock.

Thanks for the message, Brian ...

 We aren't using Mercury, so I can exclude Mercury from any responsibility. I have noted the presence of the MAILBOXP.LCK file.

Your final sentence probably concurs with my feelings about this issue. Our previous version of Pegasus (4.5-something I think) used to take about 30 second to close its main window on exit, and so, when shutting a PC down we waited until the Pegasus window closed. I have no idea why it took so long. Version 4.63 does close its window down more-or-less straight away, but maybe it isn't releasing the lock on the mailbox for some reason. Waiting half a minute before shutting down the PC can reduce the frequency of the mailbox being found locked at the next login, but it doesn't exclude it altogether, so something is going on.

Can anyone look at this issue? The problem is that it takes so long to organise the folders after a click on the "Continue" button. It would be handy of there was a way to simply stop the re-organisation of the folders when one is absolutely certain that the mailbox is not locked. For example, does deletion of the MAILBOXP.LCK file prevent the folder re-organisation stage? Would that be a safe procedure?

 Hoping for a solution soon ...

 Ken

Any ideas on this one chaps?

This issue of "Mailbox is Locked" is happening just too many times (though I must say not every time). And it is very inconvenient because it takes an age to relocate the folders.

Is there a fix? Or is there a way around it? It is definitely NOT due to a failure to close Pegasus, and even waiting for some time before shutting down the workstation is no guarantee that the issue won't recurr at the next login, whether it is on that same workstation or at another one.

Kenneth Spencer

Your locked mailbox issue is definitely not normal in v4.63.  Is there any on-access AV scanning going on in the mailbox folders?  An AV product attempting to scan the MAILBOXP.LCK file when Pegasus tries to access it to release it could cause a problem.  Double check this as I got caught having problems only to discover that an IT "professional" had removed the active scanning exclusion of the mailbox folders. 

 Also, if you are closing Pegasus using the "X" try closing using File>Exit.  In my early days of Pegasus I was convinced that closing with the "X" randomly caused closing problems.   I think I was alone in that conviction but I still always use File>Exit and recommend that method of closing to my users (I'm sure many don't use it though).

Some other things I would do to try to find additional clues:

1.  Watch the mailbox folder on the server to see how long it takes the MAILBOXP.LCK to be removed when Pegasus is closed

2.  Review the open files list in the File Server Management console to verify that all files associated with that mailbox folder are getting closed when Pegasus closes