[quote user="Brian Fluet"]

I am using Mercury in a Windows environment but have the same problem.  I first discovered it when I upgraded from v4.74 to v4.80.  See my thread here:

http://community.pmail.com/forums/thread/44383.aspx

The response made me  wonder if I was lucky that mailbox corruption didn't occur but it sound like you had users operating the same as I did with no problems.  It cerrtainly doesn't sound like it is a good idea to override the lock [/quote]

I'm sure that's true and is the way I've always understood it.

Hallo,

finally I found time to setup and test the new Mercury in my environment. Upgrade was no problem ... after I created a new self-signed certificate and changed the path/filename in every module where it's needed :-)

Environment:

Mercury V4.8 with NDS-Module
Novell Netware V6.5 (in near future Novell OES 11)
Pegasus Mail V4.7 with NDS-Module

But there is a little bug which was in Mercury - as I remember - some versions before and finally was solved (which way ever). Two scenarios:

• Starting Pegasus in NDS-Mode first creates MAILBOXP.LCK in NewMailDirectory. Starting another Mailclient accessing via Mercury and IMAP (or telling Pegasus doing that additionally) should simply create a MAILBOXM.LCK. But Thunderbird talks about wrong password and Pegasus simply talks about "some error" on the IMAP-Server.
  
• Starting some other Mailclient first accessing via IMAP, MAILBOXM.LCK is created and access is granted. Starting Pegasus afterwards it responses as if MAILBOXP.LCK would exist (for shure does not!) and have to tell Pegasus to ignore and contiunue. No further problems at all (MAILBOXP.LCK was created) and in addition Pegasus is able to start the additional IMAP-Session to same mailbox.

 With Mercury V4.73 this problem didn't exist. Did I miss something?

 Any suggestions?

Olaf

 P.S. Why not use only Pegasus? Times change and meanwhile accessing mailbox via smartphone from anywhere while Pegasus is active on the PC at their office is normal.

I am using Mercury in a Windows environment but have the same problem.  I first discovered it when I upgraded from v4.74 to v4.80.  See my thread here:

http://community.pmail.com/forums/thread/44383.aspx

The response made me  wonder if I was lucky that mailbox corruption didn't occur

but it sound like you had users operating the same as I did with no

problems.  It cerrtainly doesn't sound like it is a good idea to override the lock

What we know is that if either Mercury (MAILBOXM.LCK) or Pegasus Mail (MAILBOXP.LCK) set a lock then any other access to the mailbox is blocked.  If my IMAP users attempt to connect with a lock in place they receive some sort of password failure response.  This is not an accurate or useful response which is an additional problem.

I do not have any suggestions for a workaround.