[quote user="mikerocosm"]

Long time user, first time poster . . .

I've just converted my home Mercury server (gathers several POP3 accounts for myself and my wife, distributes them back to us through Pegasus) to deliver mail using IMAP instead of POP3. I've got it all working just fine, locally and from various remote installations, but IMAP clients will not connect to the Mercury server as long as the Pegasus client is running on the server machine (which is also my trusty does-everything home computer). Simplest solution is to just close Pegasus on the server after I've run my traps each morning, I suppose, but I never had to do that when using POP3, and Lord knows, I don't want to have to change my behavior now.

So, is there a way to configure Pegasus locally on the Mercury server so that it doesn't interfere with IMAP access from remote Pegasus clients?

Nope, the lock file is in place to ensure that a user and Mercury/32 are not both accessing the same folders at the same time.  That would be a sure way to lose data and maybe the entire folder.  This is not a problem with POP3 since it is only downloading the mail as separate files from the new mail directory.  Even when these files are downloaded and deleted via POP3 the only thing you have to do in WinPMail to clear it up is to close and reopen the new mail folder.

Inquiring minds want to know . . .

Best regards,

Mike

Long time user, first time poster . . .

I've just converted my home Mercury server (gathers several POP3 accounts for myself and my wife, distributes them back to us through Pegasus) to deliver mail using IMAP instead of POP3. I've got it all working just fine, locally and from various remote installations, but IMAP clients will not connect to the Mercury server as long as the Pegasus client is running on the server machine (which is also my trusty does-everything home computer). Simplest solution is to just close Pegasus on the server after I've run my traps each morning, I suppose, but I never had to do that when using POP3, and Lord knows, I don't want to have to change my behavior now.

So, is there a way to configure Pegasus locally on the Mercury server so that it doesn't interfere with IMAP access from remote Pegasus clients?

Inquiring minds want to know . . .

Best regards,

Mike

Running Pegasus Mail sets a lockfile so any IMAP connections are denied.

IMAP & Pegasus both work with the 'folder structure' (*.PM? files) and using both at the same time will guarantee file corruption and data loss.

POP on the other hand only downloads messages fron the 'INBOX' (the individual *.cnm files) so there is no issue (except maybe out of date INBOX list in Pegasus that a refresh will fix).

So to use IMAP, PM (in local file mode) *MUST* be shut down.