[quote user="Thomas R. Stephenson"]

I do not know what is happening here.  It might be that the local cache is messed up.  Right click on the folder and clear the cache.

[/quote]

Hi Thomas,

I tried both "Refresh this Folder" and "Cache all messages" options on right-click menu, but no success.

My idea is to provide a single IMAP Profile(user) to which my family members will login from outlook and move their messages to, and then logging in to Pmail, create their own trays/folder structure as required and copy back all the moved messages.

Thanks & Regards,

Rad.

Hi,

I am trying to migrate my Outlook 2003 mail to Pegasus Mail v4.52 for user Admin.
I am using IMAP folder and Mercury v4.72 for the same.

Taking clues from the forum, I have done the following:

- Installed Mercury for loacalhost (127.0.0.1), and linked it with PMail (gateway).
- Created IMAP profile in PMail using 127.0.0.1 as server and Admin login details.
- Created a new IMAP email account in Outlook 2003 using 127.0.0.1 as IMAP server and PMail Admin login details.

Now in Outlook, I can access my new IMAP folder and move required emails into it.
On invoking PMail, I can access the same mails in my New Mail folder.
I assume I will have to move all my mails from individual folders manually using this method.

Is there any other way to migrate my Outlook mail "Folders" structures to PMail "Trays"?

I have another query.
====================

When I try to connect to IMAP folder from PMail, I get the following error:
----------------------
Profile 'OutlookMail':
The IMAP server that manages this mailbox or folder has reported an error during the operation you have attempted to perform.
The operation cannot be completed.
----------------------

The Mercury IMAP4 Server displays following details:
----------------------
Connection from 127.0.0.1, Fri Dec 10 07:12:23 2010
Admin at 127.0.0.1: 0 sec. elapsed, connection closed Fri Dec 10 07:12:23 2010
----------------------

How do I display (connect to) IMAP folder under Admin in PMail?

Thanks & Regards,
Rad.

You cannot convert your Outlook folders to Pegasus trays. You will need to do that manually.

There are quite specific rules about two machines accessing a Mercury IMAP folder at the same time. If you have the wrong settings, it is a very bad thing to do. Perhaps that is the issue?

[quote user="Sharkfin"]

You cannot convert your Outlook folders to Pegasus trays. You will need to do that manually.

There are quite specific rules about two machines accessing a Mercury IMAP folder at the same time. If you have the wrong settings, it is a very bad thing to do. Perhaps that is the issue?

[/quote]

Hi Sharkfin,

I have both Outlook and PMail on my laptop.

I successfully moved all my Outlook2003 mail to Pmail 4.52 using IMAP. I created IMAP profiles for users on Mercury/PMail side and linked Mercury to PMail by Mercury Gateway. On outlook side, I created IMAP account using first PMail user's login details.

Then at a time, I opened Outlook and connected IMAP to a specific user, moved required mails from specific folder to IMAP, closed Outlook. Again opened PMail for that user, where all my was present in Mew Mail folder. I created the required Trays under Main Folder, and moved my mail there. It took a while but I have all my mails under PMail.

Now after completing the migration, I have removed the Mercury Gateway using pconfig to allow PMail to send mail on its own. As Outlook is not being used now, shouldn't PMail users be allowed to access their respective IMAP profiles (display IMAP folder under My mailbox tree). The Connect button in IMAP profile displays the following error:

------------------------------------------------

Profile 'IMAPprofile':
The IMAP server that manages this mailbox or folder has reported an error during the operation you have attempted to perform.
The operation cannot be completed.
------------------------------------------------

Thanks & Regards,

Rad.

> Now after completing the migration, I have removed the Mercury Gateway using pconfig to allow PMail to send mail on its own.
> As Outlook is not being used now, shouldn't PMail users be allowed to access their respective IMAP profiles (display IMAP
> folder under My mailbox tree). The Connect button in IMAP profile displays the following error:
> ------------------------------------------------
> Profile 'IMAPprofile':
> The IMAP server that manages this mailbox or folder has reported an error during the operation you have attempted to perform.
> The operation cannot be completed.
> ------------------------------------------------

Turn on session logging in Tools | Internet options | General and try again.  The session log will be very useful in finding out why Pegasus Mail cannot connect to a IMAP4 server.

[quote user="Thomas R. Stephenson"]

Turn on session logging in Tools | Internet options | General and try again.  The session log will be very useful in finding out why Pegasus Mail cannot connect to a IMAP4 server.

[/quote]

Hi Thomas,

I selected the "session log" option under Internet Options, but which log file should I check? I couldn't locate one.

The IMAP.PM file in my mailbox folder has following data:

Profile: "IMAPprofile",28672,"127.0.0.1",143,"Admin",19011,"=5(+2","",0,30,0,"","",0,"Trash"
Profile-ID: 1000

-----------------------------------------------------------------------------------------

Thanks & Regards,

Rad.

Somehow my selecting the create session log option in Internet Options is not getting saved.

When I logout and login again into PMail, sessions log option is always un-ticked.

Thanks & Regards,

Rad.

> I selected the "session log" option under Internet Options, but which log file should I check? I couldn't locate one.

> The IMAP.PM file in my mailbox folder has following data:

The file is a TCP????.WPM file in your home mail directory.  You get one for each session with the server, POP3, IMAP4 or SMTP.

> Somehow my selecting the create session log option in Internet Options is not getting saved.

It's not supposed to be saved.  This is only active for the current session.

[quote user="Thomas R. Stephenson"]

> I selected the "session log" option under Internet Options, but which log file should I check? I couldn't locate one.

> The IMAP.PM file in my mailbox folder has following data:

The file is a TCP????.WPM file in your home mail directory.  You get one for each session with the server, POP3, IMAP4 or SMTP.

[/quote]

Hi Thomas,

Thanks for pointing out the log file.

This log file TCP0001.WPM has the following details:

-----------------------------------------------------------------------------

--- Mon, 20 Dec 2010 07:24:02 ---
Connect to '127.0.0.1' port 143, timeout 30.
07:24:02.264 [*] Connection established to 127.0.0.1
07:24:02.374 >> 0057 * OK localhost IMAP4rev1 Mercury/32 v4.72 server ready.\0D\0A
07:24:02.374 << 0015 A1 CAPABILITY\0D\0A
07:24:02.374 >> 0047 * CAPABILITY IMAP4rev1 AUTH=PLAIN X-MERCURY-1\0D\0A
07:24:02.374 >> 0028 A1 OK CAPABILITY complete.\0D\0A
07:24:02.374 << 0026 A2 LOGIN "Admin" "xxxxx"\0D\0A
07:24:02.414 >> 0070 A2 NO Error attaching to mailbox (may be in use by another process).\0D\0A
07:24:02.414 --- Connection closed normally at Mon, 20 Dec 2010 07:24:02. ---\0A\0A

--- Tue, 21 Dec 2010 07:51:26 ---
Connect to '127.0.0.1' port 143, timeout 30.
07:51:26.541 [*] Connection established to 127.0.0.1
07:51:27.571 >> 0057 * OK localhost IMAP4rev1 Mercury/32 v4.72 server ready.\0D\0A
07:51:27.571 << 0015 A1 CAPABILITY\0D\0A
07:51:27.571 >> 0047 * CAPABILITY IMAP4rev1 AUTH=PLAIN X-MERCURY-1\0D\0A
07:51:27.571 >> 0028 A1 OK CAPABILITY complete.\0D\0A
07:51:27.571 << 0026 A2 LOGIN "Admin" "xxxxx"\0D\0A
07:51:27.601 >> 0070 A2 NO Error attaching to mailbox (may be in use by another process).\0D\0A
07:51:27.601 --- Connection closed normally at Tue, 21 Dec 2010 07:51:27. ---\0A\0A

-----------------------------------------------------------------------------

Looks like the IMAP mailbox is getting locked somehow.

But I am the only user on my laptop using PMail. Also, Outlook is not running when PMail is active.

What could be locking the mailbox?

Thanks & Regards,

Rad.

> Hi Thomas,
> Thanks for pointing out the log file.
> This log file TCP0001.WPM has the following details:
> -----------------------------------------------------------------------------
>
> --- Mon, 20 Dec 2010 07:24:02 ---
> Connect to '127.0.0.1' port 143, timeout 30.
> 07:24:02.264
> Connection established to 127.0.0.1
> 07:24:02.374 >> 0057 * OK localhost IMAP4rev1 Mercury/32 v4.72 server ready.\0D\0A
> 07:24:02.374 << 0015 A1 CAPABILITY\0D\0A
> 07:24:02.374 >> 0047 * CAPABILITY IMAP4rev1 AUTH=PLAIN X-MERCURY-1\0D\0A
> 07:24:02.374 >> 0028 A1 OK CAPABILITY complete.\0D\0A
> 07:24:02.374 << 0026 A2 LOGIN "Admin" "xxxxx"\0D\0A
> 07:24:02.414 >> 0070 A2 NO Error attaching to mailbox (may be in use by another process).\0D\0A
> 07:24:02.414 --- Connection closed normally at Mon, 20 Dec 2010 07:24:02. ---\0A\0A
>
> --- Tue, 21 Dec 2010 07:51:26 ---
> Connect to '127.0.0.1' port 143, timeout 30.
> 07:51:26.541
> Connection established to 127.0.0.1
> 07:51:27.571 >> 0057 * OK localhost IMAP4rev1 Mercury/32 v4.72 server ready.\0D\0A
> 07:51:27.571 << 0015 A1 CAPABILITY\0D\0A
> 07:51:27.571 >> 0047 * CAPABILITY IMAP4rev1 AUTH=PLAIN X-MERCURY-1\0D\0A
> 07:51:27.571 >> 0028 A1 OK CAPABILITY complete.\0D\0A
> 07:51:27.571 << 0026 A2 LOGIN "Admin" "xxxxx"\0D\0A
> 07:51:27.601 >> 0070 A2 NO Error attaching to mailbox (may be in use by another process).\0D\0A
> 07:51:27.601 --- Connection closed normally at Tue, 21 Dec 2010 07:51:27. ---\0A\0A
>
> -----------------------------------------------------------------------------
> Looks like the IMAP mailbox is getting locked somehow.

Are you running Pegasus Mail against Mercury?  Is Pegasus Mail pointing at the mailbox on the Mercury host or Mercury pointing at the Pegasus Mail mailbox?  

I any case if there is a mailboxp.lck file in the Mercury mailbox directory it will lockout access to the IMAP4 client.  

> But I am the only user on my laptop using PMail. Also, Outlook is not running when PMail is active.
> What could be locking the mailbox?

Pegasus Mail if Mercury and Pegasus Mail are looking at the same mail directories.

[quote user="Thomas R. Stephenson"]> Hi Thomas,
Are you running Pegasus Mail against Mercury?  Is Pegasus Mail pointing at the mailbox on the Mercury host or Mercury pointing at the Pegasus Mail mailbox?  

I any case if there is a mailboxp.lck file in the Mercury mailbox directory it will lockout access to the IMAP4 client.  
[/quote]

Hi Thomas,

Can you please explain the setup for accessing Mercury IMAP folder via PMail? What is running PMail against Mercury? I didn't quite get it.

I have Mercury running on 127.0.0.1 (MercuryS, MercuryP, MercuryC, MercuryD, MercuryI). Mercury does not have mailboxp.lck file under D:\MERCURY\MAIL\Admin. The folder is empty. The D:\MERCURY\MAIL folder has only PMAIL.USR file.

PMail has an IMAP profile created for Admin using server address 127.0.0.1, port 143, timeout not specified, Admin login details, Mailbox reference spaces.

Thanks & Regards,

Rad.

> Hi Thomas,

> Can you please explain the setup for accessing Mercury IMAP folder via PMail? What is running PMail against Mercury? I didn't quite get it.

Assuming that you are not using a secure MercuryI setup it is simplicity itself.  You enter the host name or IP address of the system running Mercury, user name and password that is shown in the Mercury mail directory passwrd.pm file.

>
> I have Mercury running on 127.0.0.1 (MercuryS, MercuryP, MercuryC, MercuryD, MercuryI). Mercury does not have mailboxp.lck file under
> D:\MERCURY\MAIL\Admin. The folder is empty. The D:\MERCURY\MAIL folder has only PMAIL.USR file.

What does Pegasus Mail show with Help | About Pegasus Mail | Info?  Paste it here.  You can also paste a copy of the Mercury.ini file.

Also turn on session logging in Tools | Internet options | General and paste the results shown in the TCPxxxx.WPM file here.  Munge the password but nothing else.

>
> PMail has an IMAP profile created for Admin using server address 127.0.0.1, port 143, timeout not specified, Admin login details,
> Mailbox reference spaces.

I'm trying to figure out your structure, it is still not clear how you are setup.  The data I have asked for will help a lot.

Hi Thomas,

Providing the details as suggested:

> What does Pegasus Mail show with Help | About Pegasus Mail | Info?  Paste it here.

Pegasus Mail for Microsoft Windows
Copyright (C) 1992-2010, David Harris, all rights reserved
Electronic mail to support@pmail.gen.nz.

WinPMail version: Version 4.52 (Win32), Jan 13 2010
Language resources: Standard UK English resource set
Extension Manager version: 1.13
Operating mode: Standalone
User name and ID: Admin, 0
Windows version: 5.1
Windows flag word: 0
WINPMAIL.EXE directory: D:\PMAIL\Programs
Home mailbox location: D:\PMAIL\MAIL\Admin
New mailbox location: D:\PMAIL\MAIL\Admin
TMP environment variable: C:\DOCUME~1\Rad\LOCALS~1\Temp
TEMP environment variable: C:\DOCUME~1\Rad\LOCALS~1\Temp
LAN-based SMTP support: N, N, N
NetWare MHS support: N, N, N
Built-in TCP/IP support: Enabled
  - WINSOCK version: WinSock 2.0
  - WINSOCK path: C:\WINDOWS\system32\WSOCK32.DLL
Commandline: -roam -A
Active -Z options: 32768
PMR variable: (None)
PML variable: (None)
MAI variable: (None)
NB variable: (None)
Autofiltering folders: 77 (77 active, 0 inactive)
Last new mail count: 2

>You can also paste a copy of the Mercury.ini file.

#  MERCURY.INI generated by Mercury Setup
#
#
#  Sample Bindery Mode / Standalone Mode MERCURY.INI file.
#  This sample file implements most of the possible switches for each
#  module, but you can edit it to do less if you wish.
#
#  Anything after a '#' to the end of the line is a comment and
#  is stripped out before parsing. Trailing and leading whitespace
#  is also stripped before parsing. Many sample commands have been
#  left in this file commented out for reference purposes.
#
#  Note that in general, manual modification of this file is NOT
#  RECOMMENDED - use the Mercury "Configuration" menu to change the
#  program's settings wherever possible.
#

[General]
myname:          localhost    # Canonical name for this server
timezone:        +0530    # Time Zone to add to date fields
file_api:        1    # Use the file api instead of queues
mailqueue:       D:\MERCURY\QUEUE    # Where mail should be put for delivery
smtpqueue:       D:\MERCURY\QUEUE    # Where the SMTP client should look for mail
newmail_path:    D:\PMAIL\MAIL\~N    # Where to find the users' WinPMail mailboxes.

[Protocols]
MERCURYS.DLL
MERCURYP.DLL
# MERCURYE.DLL
MERCURYC.DLL
MERCURYD.DLL
# MERCURYH.DLL
# MERCURYF.DLL
# MERCURYW.DLL
# MERCURYX.DLL
MERCURYI.DLL
# MERCURYB.DLL

[Mercury]
failfile:      D:\MERCURY\Mercury\FAILURE.MER    # Delivery failure notification template
confirmfile:   D:\MERCURY\Mercury\CONFIRM.MER    # Delivery confirmation template
aliasfile:     D:\MERCURY\Mercury\ALIAS.MER    # System-wide alias file
synfile:       D:\MERCURY\Mercury\SYNONYM.MER    # User synonym database
listfile:      D:\MERCURY\Mercury\LISTS.MER    # List of lists
logfile:       D:\MERCURY\Logs\Core\~y-~m-~d.log    # Traffic logging file
logwidth:      30    # Width of address fields in logfile
retpath:       1    # Do/Don't use 'return-path' for errors
maxhops:       30    # Used to detect mailing loops
gullible:      0    # If NZ, don't validate 'From' fields
poll:          10   # Seconds between queue polling cycles
scratch:       D:\MERCURY\Scratch    # Where we can write temp files
returnlines:   15    # How many lines of failed messages to return
postmaster:    Admin    # NetWare UIC of postmaster
broadcast:     1    # Yes, we want broadcast notifications, but
receipts:      0    # ... no broadcasts for receipt confirmations
PM_notify:     1    # Do/Don't send errors to the postmaster
change_owner:  1    # Change message ownership to recipient
auto_tzone:    1    # If NZ, obtain timezone information from OS
LogLevel:      15    # System message reporting level
LogMax:        100    # Maximum number of system messages to store
RetryPeriod:   5    # Period between job retries (minutes)
MaxRetries:    16    # Maximum number of times a job can fail
TwoPasses:     1    # If NZ, process submission queue in 2 passes
Autoaddress:   -128    # If NZ, auto-generate user addresses based on name
Daily_exit:    0    # If NZ, auto-restart each day after maintenance
No_Areply:     0    # If NZ, disable automatic replies system-wide
Alt_Forward:   0    # If NZ, allow alternate forwarding specification
Maint_hour:    2    # Hour for daily maintenance (24-hour clock)
Maint_min:     0    # Minute for daily maintenance
Retry_Mode:    0    # If NZ, use progressive backoff for queue retries
Local_DSNs:    1    # If NZ generate Delivery Status for local users only
DSN_time1:     10800    # Seconds deferred before first DSN is sent
DSN_time2:     86400    # Seconds deferred before second DSN is sent
DSN_time3:     259200    # Seconds deferred before third DSN is sent
Host_in_title: 0    # If NZ, show hostname in system tray and taskbar
Lingering:     0    # Enable or disable 'lingering mailboxes'
Linger_Timeout: 60   # Seconds before a lingering mailbox is shut down
Alert_Host:    notify.pmail.com    # Host to check for licensee advisories
Alert_Interval: 720   # Frequency in minutes (min 240) for checks
Alert_Flags:   3    # Flags controlling advisory checks

[MercuryC]
Host : smtp.gmail.com
Failfile : D:\MERCURY\Mercury\FAILURE.MER
Poll : 30
Scratch : D:\MERCURY\scratch
ReturnLines : 15
Timeout : 30
ESMTP : 1
Server_Port : 465
SMTP_Username: abcd
SMTP_Password: xxxxxxxx
SMTP_ConnFlags : 8
POP3_Auth : 1
POP3_Host : pop.gmail.com
POP3_Port : 995
POP3_ConnFlags : 8
Logfile : D:\MERCURY\Logs\MercuryC\~y-~m-~d.log
Log_Verbose : 0
Session_logging : D:\MERCURY\Sessions\MercuryC
Session_logmode : 0

[MercuryE]
Session_logging : D:\MERCURY\Sessions\MercuryE
Session_logmode : 0
Poll : 15
Timeout : 60
Logfile : D:\MERCURY\Logs\MercuryE\~y-~m-~d.log
Log_Verbose : 0
DNS_Timeout : 20
DNS_Retries : 4
Transcripts : 1
MaxThreads : 10

[MercuryD]
Scratch : D:\MERCURY\Scratch\MercuryD
Timeout : 30
Poll : 30
Session_logging : D:\MERCURY\Sessions\MercuryD
Session_logmode : 0

[MercuryS]
Debug : 1
Logfile : D:\MERCURY\Logs\MercuryS\~y-~m-~d.log
Timeout : 30
Relay : 0
Strict_Relay : 0
Interface : 127.0.0.1
Allow_Illegals : 0
SMTP_Authentication : 0
Session_logging : D:\MERCURY\Sessions\MercuryS
Session_logmode : 0
Compliance_Settings : 0
Maximum_Failed_Rcpts : 4
Max_Relay_Attempts : 4
SSL_Mode : 0
ST_Blacklisting : 288
No_VRFY : 0
SMTP_ConnFlags : 0

[MercuryP]
Scratch : D:\MERCURY\Scratch\MercuryP
Logfile : D:\MERCURY\Logs\MercuryP\~y-~m-~d.log
Stack : 32768
Mark_Read : 1
SSL_Mode : 0
Login_Disabled : 0
UIDL_nul_list : 1
New_UIDs : 1
No_NUL_passwords : 1
Session_logging : D:\MERCURY\Sessions\MercuryP
Session_logmode : 0
Timeout : 60

[MercuryX]
Cmd_Wait: 1
IE4_Dialling: 0
Use_ETRN: 0
Clients_only: 0
Drain_queues: 1
Sunday: 0000,0000,0,0,0,0
Monday: 0000,0000,0,0,0,0
Tuesday: 0000,0000,0,0,0,0
Wednesday: 0000,0000,0,0,0,0
Thursday: 0000,0000,0,0,0,0
Friday: 0000,0000,0,0,0,0
Saturday: 0000,0000,0,0,0,0

[Domains]
127.0.0.1: Localhost
localhost: Localhost

[Maiser]
Maiser:          Maiser   # 'Username' of mail server account
Helpfile:        D:\MERCURY\Mercury\MAISER.HLP   # Help sent on failed maiser requests
Lookupfile:      D:\MERCURY\Mercury\MAISER.LKP   # Format file for the 'lookup' command
Send_dir:        D:\MERCURY\Mercury\SENDABLE   # Directory for the 'send' command
Logfile:         D:\MERCURY\Logs\Maiser\~y-~m-~d.LOG   # Mail server log file
Notify:          D:\MERCURY\Mercury\TMP   # Dir. for pending 'notify' commands
NoList:          N   # If 'Y', disable the 'list' command
Local_only:      Y   # If 'Y', local 'notify' commands only

[MercuryH]
Logfile : D:\MERCURY\Logs\MercuryH\~y-~m-~d.log
Timeout : 30

[MercuryI]
Scratch : D:\MERCURY\Scratch\MercuryI
Logfile : D:\MERCURY\Logs\MercuryI\~y-~m-~d.log
Timeout : 120
Server_Port : 143
SSL_Port: 993
Charset : ISO-8859-1
Session_logging : D:\MERCURY\Sessions\MercuryI
Session_logmode : 0
Idle_Timeout : 1800
SSL_Mode : 0
Login_Disabled : 0
No_NUL_passwords : 1

[MercuryB]
Scratch : D:\MERCURY\Scratch\MercuryB
Logfile : D:\MERCURY\Logs\MercuryB\~y-~m-~d.log
Timeout : 120
Server_Port : 80
Session_logging : D:\MERCURY\Sessions\MercuryB
Session_logmode : 0
Idle_Timeout : 1800
SSL_Mode : 0
Alt_Server_Port : 443

[Groups]

[Rewrite]

[Statistics]
StatFlags:    0  # Statistical reporting settings
STF_Hours:    24  # How often to write stat log files
STM_Hours:    24  # How often to e-mail stat log files

>Also turn on session logging in Tools | Internet options | General and paste the results shown in the TCPxxxx.WPM file here.  Munge the password but nothing else.

--- Mon, 20 Dec 2010 07:24:02 ---
Connect to '127.0.0.1' port 143, timeout 30.
07:24:02.264 [*] Connection established to 127.0.0.1
07:24:02.374 >> 0057 * OK localhost IMAP4rev1 Mercury/32 v4.72 server ready.\0D\0A
07:24:02.374 << 0015 A1 CAPABILITY\0D\0A
07:24:02.374 >> 0047 * CAPABILITY IMAP4rev1 AUTH=PLAIN X-MERCURY-1\0D\0A
07:24:02.374 >> 0028 A1 OK CAPABILITY complete.\0D\0A
07:24:02.374 << 0026 A2 LOGIN "Admin" "xxxxxxxxxx"\0D\0A
07:24:02.414 >> 0070 A2 NO Error attaching to mailbox (may be in use by another process).\0D\0A
07:24:02.414 --- Connection closed normally at Mon, 20 Dec 2010 07:24:02. ---\0A\0A

--- Tue, 21 Dec 2010 07:51:26 ---
Connect to '127.0.0.1' port 143, timeout 30.
07:51:26.541 [*] Connection established to 127.0.0.1
07:51:27.571 >> 0057 * OK localhost IMAP4rev1 Mercury/32 v4.72 server ready.\0D\0A
07:51:27.571 << 0015 A1 CAPABILITY\0D\0A
07:51:27.571 >> 0047 * CAPABILITY IMAP4rev1 AUTH=PLAIN X-MERCURY-1\0D\0A
07:51:27.571 >> 0028 A1 OK CAPABILITY complete.\0D\0A
07:51:27.571 << 0026 A2 LOGIN "Admin" "xxxxxxxxxx"\0D\0A
07:51:27.601 >> 0070 A2 NO Error attaching to mailbox (may be in use by another process).\0D\0A
07:51:27.601 --- Connection closed normally at Tue, 21 Dec 2010 07:51:27. ---\0A\0A

--- Wed, 22 Dec 2010 09:24:58 ---
Connect to '127.0.0.1' port 143, timeout 30.
09:24:58.633 [*] Connection established to 127.0.0.1
09:24:58.643 >> 0057 * OK localhost IMAP4rev1 Mercury/32 v4.72 server ready.\0D\0A
09:24:58.643 << 0026 A1 LOGIN "Admin" "xxxxxxxxxx"\0D\0A
09:24:58.653 >> 0070 A1 NO Error attaching to mailbox (may be in use by another process).\0D\0A
09:24:58.653 --- Connection closed normally at Wed, 22 Dec 2010 09:24:58. ---\0A\0A


Thanks & Regards,

Rad.

Help | About Pegasus Mail | Info

> WINPMAIL.EXE directory: D:\PMAIL\Programs
> Home mailbox location: D:\PMAIL\MAIL\Admin
> New mailbox location: D:\PMAIL\MAIL\Admin

Mercury.ini

> newmail_path:    D:\PMAIL\MAIL\~N    # Where to find the users' WinPMail mailboxes.

The ~N is replaced by the username that matches a subdirectory.

> --- Tue, 21 Dec 2010 07:51:26 ---
> Connect to '127.0.0.1' port 143, timeout 30.
> 07:51:26.541 Connection established to 127.0.0.1
> 07:51:27.571 >> 0057 * OK localhost IMAP4rev1 Mercury/32 v4.72 server ready.\0D\0A
> 07:51:27.571 << 0015 A1 CAPABILITY\0D\0A
> 07:51:27.571 >> 0047 * CAPABILITY IMAP4rev1 AUTH=PLAIN X-MERCURY-1\0D\0A
> 07:51:27.571 >> 0028 A1 OK CAPABILITY complete.\0D\0A
> 07:51:27.571 << 0026 A2 LOGIN "Admin" "xxxxxxxxxx"\0D\0A
> 07:51:27.601 >> 0070 A2 NO Error attaching to mailbox (may be in use by another process).\0D\0A
> 07:51:27.601 --- Connection closed normally at Tue, 21 Dec 2010 07:51:27. ---\0A\0A

Trying to connect as Admin with IMAP4 while running Pegasus mail as Admin in the direct mode.  The MAILBOXP.LCK should be in place in the admin directory.  Unless this is on two separate systems here is the problem.  Pegasus Mail and Mercury are both using the same directory structure.  You cannot access the same mailbox (Admin) with Pegasus Mail and an IMAP4 connection.  Now if there is a different account on the Mercury system you can make an IMAP4 connection.

[quote user="Thomas R. Stephenson"]

Trying to connect as Admin with IMAP4 while running Pegasus mail as Admin in the direct mode.  The MAILBOXP.LCK should be in place in the admin directory.  Unless this is on two separate systems here is the problem.  Pegasus Mail and Mercury are both using the same directory structure.  You cannot access the same mailbox (Admin) with Pegasus Mail and an IMAP4 connection.  Now if there is a different account on the Mercury system you can make an IMAP4 connection.

[/quote]

Thanks Thomas. Got the idea.

I could login to other user account under mercury. Now when I login to IMAP folder, I can see the email counts for respective folders for that user like 2:2, 3:0, etc.

But when I click these folders under IMAP, no email details are displayed in right panel and after a while the email count vanishes.

How do I get to access these mails?

Thanks & Regards,

Rad.

> I could login to other user account under mercury. Now when I login

to IMAP folder, I can see the email counts for respective folders
> for

that user like 2:2, 3:0, etc.

> But when I click these folders

under IMAP, no email details are displayed in right panel and after a

while the email count vanishes.

I do not know what is happening here.  It might be that the local cache is messed up.  Right click on the folder and clear the cache.