You will also get the opening warning if MAILBOXM.LCK exists.

Unlike MAIMBOXP.LCK it is not erased when Pmail is closed properly.

Bob

When I start Pegasus, many times I get a message that the mailbox is open and I am required to click the "Continue" button. This happens on only 1 of the 4 computers on which I regularly use Pegasus. Any suggestions for a cure?

[quote user="lhhesscpa"]When I start Pegasus, many times I get a message that the mailbox is open and I am required to click the "Continue" button. This happens on only 1 of the 4 computers on which I regularly use Pegasus. Any suggestions for a cure?
[/quote]

My only guess here is that one of the systems is not closing properly and removing the lock file.  This file is removed when closing  as long as there is a normal close.

By normal close I assume you mean File > Exit. If so, the problem occurs even when I do that. BTW, would a normal close also include logging off Win XP while the app. is running? Would it help to manually delete the lock file? And, if so, what is its name?

[quote user="lhhesscpa"]By normal close I assume you mean File > Exit. If so, the problem occurs even when I do that. BTW, would a normal close also include logging off Win XP while the app. is running? Would it help to manually delete the lock file? And, if so, what is its name?
[/quote]

Logging out is not a normal close.  It may of may not work, I've never had a problem with the program responding the the OS close command but other have when the OS does not all sufficient time for the complete close.  The lock file is MAILBOXP.LCK.

Is it correct to assume that that file is not present when the app. is closed?

[quote user="lhhesscpa"]Is it correct to assume that that file is not present when the app. is closed?
[/quote]

Correct, if properly closed the file is removed.   

I suppose the lock file is Pegasus only way to know that it wasn't properly shut down. So clicking the "Continue" button would tell Pegasus to disregard the lock file and possibly do some clean-up.

Manually deleting the file would prevent any such clean-up, which could cause new problems. (Speaking from experience with other applications, not actually knowing

if Pegasus does more than just delete/reuse the lock file.)

Just my five cents, of course.

Erik 

Right. Since I can recover with the Continue button, I don't think I'm going to delete the lock file. I'd sure like to know why the cleanup so frequently isn't completed. I'm hoping the developer will have some idea.

Some wild guesses, if case you haven't already checked these: 

Obviously, most any application needs time for its bookkeeping during shutdown. I have noticed Pegasus being a bit slow when interrupted in the middle of network activity, perhaps blocking on an operating system call. And I have noticed that operating systems and network stacks behave differently. Perhaps some combination of software or configuration on that particular computer blocks long enough for the OS to kill it during shutdown?

To avoid the lock file problem on my XP Pro box, I have to close Pegasus before shutdown. Others don't seem to have this problem. (I also go into Offline mode before putting my portable to sleep - Pegasus isn't tired at all, and is very stubborn trying to fetch email from the unconnected network ;-)

Erik 

[quote user="lhhesscpa"]Right. Since I can recover with the Continue button, I don't think I'm going to delete the lock file. I'd sure like to know why the cleanup so frequently isn't completed. I'm hoping the developer will have some idea.
[/quote]

He would be saying what everyone else is saying, for some reason Pegasus mail was not given time to completely shutdown when last run.   The deletion of the lock file is one of the last things accomplished and if the system is shutdown without closing the program the OS may not be giving the program time to completely close.  This is especially true in a network environment where the mailboxes are on a server.

We get this regularly, when users 'forget' to close Pegasus before logoff/shutdown. Sometimes, we get folder index errors too.

Thomas is correct; depending on how many messages you have, how big they are and what Pegasus has been told to do with the messages (filtering?), Windows logoff/shutdown may not allow sufficient time to complete the tasks before it 'kills' the program. This effect is more pronounced when the mailboxes are hosted on a server, which has a virus scanner protecting it (as it should, of course). Since scanning files slows down the folder updates, it becomes a lot easier to overrun the couple of seconds that Windows allows for a graceful termination. Hence, Pegasus is effectively crashed out in the middle of whatever it was doing at the time.

The result is more than just annoying. We are using SquirrelMail for remote access and Mercury will refuse to allow access to a mailbox (using IMAP), which has the 'in use' flag set. So users who are sloppy about shutting down Pegasus at the end of the day, then start complaining to us that they couldn't use SquirrelMail in the evening.

We also get it when users 'inadvertently' access the same mailbox from multiple PC's (i.e. they logon elsewhere and try to check their mail, when it is still open at a previous PC). Frankly, I've no idea how to stop that happening. I so wish Active Directory could restrict users to a single logon session, like Netware!