Community Discussions and Support
subsequent activation of Mercury I (additional to C, D, X)

Hello Community, 

We are using the modules C, D and X of Mercury 4.01 since many years. The Mercury system installed on a server works together with Pegasus Mail on different workstations. It's a very stable and reliable email system. The Pegasus Clients with different users (multi user) are directly connected to Mercury by using the pmgate.sys file for assigning the user mailboxes on the server.

Now we would like to give our street workers the opportunity to check their mails, which are collected and distributed by the "Mercury D". The street workers use a VPN to connect from remote to the local LAN. Presently they can start their PMail Client, which open all folders in their mailboxes on the Mercury System. But this takes to much time, because of loading all folders and all mails (app. more than 10 minutes via the VPN). That's why we would like to use the "Mercury I".

Is it possible to activate/install the "Mercury I" subsequently to the existing Mercury Modules without changing the current system? Is "Mercury I" able to use the existing folder structure of each existing user mailbox which was created by PMail (Some of our users have extended folder structures with many subfolders)? For example, I know that "Mercury I" does not support "folders in folders". That's why, are there any problems to be expected? Is it possible to simultaneously access to an user mailbox by IMAP4 from remote and by PMail from local LAN?

 regards from Germany

 
Joerg
 

<p>Hello Community, </p><p>We are using the modules C, D and X of Mercury 4.01 since many years. The Mercury system installed on a server works together with Pegasus Mail on different workstations. It's a very stable and reliable email system. The Pegasus Clients with different users (multi user) are directly connected to Mercury by using the pmgate.sys file for assigning the user mailboxes on the server.</p><p>Now we would like to give our street workers the opportunity to check their mails, which are collected and distributed by the "Mercury D". The street workers use a VPN to connect from remote to the local LAN. Presently they can start their PMail Client, which open all folders in their mailboxes on the Mercury System. But this takes to much time, because of loading all folders and all mails (app. more than 10 minutes via the VPN). That's why we would like to use the "Mercury I". </p><p>Is it possible to activate/install the "Mercury I" subsequently to the existing Mercury Modules without changing the current system? Is "Mercury I" able to use the existing folder structure of each existing user mailbox which was created by PMail (Some of our users have extended folder structures with many subfolders)? For example, I know that "Mercury I" does not support "folders in folders". That's why, are there any problems to be expected? Is it possible to simultaneously access to an user mailbox by IMAP4 from remote and by PMail from local LAN?</p><p> regards from Germany</p><p>  Joerg  </p>

Yes, all that is needed is to turn it on and re-start Mercury, it uses the same username and password as the POP3 access.  .  That said, I would think about providing them with web mail access using something like SquirrelMail since this only requires them to have web access.  I did this for our "road warriors" since they were not always assured of anything other then browser access through various firewalls.

 

<p>Yes, all that is needed is to turn it on and re-start Mercury, it uses the same username and password as the POP3 access.  .  That said, I would think about providing them with web mail access using something like SquirrelMail since this only requires them to have web access.  I did this for our "road warriors" since they were not always assured of anything other then browser access through various firewalls. </p><p> </p>

Dear Thomas,

Thanks for your quick reply. But why you need an additional email client like SquirrelMail when accessing via webmail by browser?

Does Mercury grant web access. Which Mercury module has this functionality?

 

regards

 

Joerg
 

<p>Dear Thomas,</p><p>Thanks for your quick reply. But why you need an additional email client like SquirrelMail when accessing via webmail by browser?</p><p>Does Mercury grant web access. Which Mercury module has this functionality?</p><p> </p><p>regards</p><p> </p><p>Joerg  </p>

There is presently no webmail module in Mercury, but you can use SquirrelMail or some other separate webmail solution with Mercury. To do this you will first need to activate the IMAP module in Mercury.

/Rolf
 

<p>There is presently no webmail module in Mercury, but you can use SquirrelMail or some other separate webmail solution with Mercury. To do this you will first need to activate the IMAP module in Mercury.</p><p>/Rolf  </p>

Dear Rolf,

It seems I have a little lack of clarity. Webmail

means to me, that I can access to my mailbox by using an ordinary

browser and therefore the mailbox system offers a webservice via port

80. If I need an additional client for acces via IMAP4, then it is not

really a Webmail service. And than I can also use PMail for it.

 

Nice after office hours. Now it's 17:38 in Germany. Until tomorrow 

 

Joerg

<p>Dear Rolf,</p><p>It seems I have a little lack of clarity. Webmail means to me, that I can access to my mailbox by using an ordinary browser and therefore the mailbox system offers a webservice via port 80. If I need an additional client for acces via IMAP4, then it is not really a Webmail service. And than I can also use PMail for it.</p><p> </p><p>Nice after office hours. Now it's 17:38 in Germany. Until tomorrow </p><p> </p><p>Joerg </p>

[quote user="Joerg"]

Dear Thomas,

Thanks for your quick reply. But why you need an additional email client like SquirrelMail when accessing via webmail by browser?

Does Mercury grant web access. Which Mercury module has this functionality?

regards

Joerg

[/quote]

MercuryI provides IMAP4 access to any IMAP4 mail client via port 143.  If the users are coming in via a VPN connection then this should be all that is required to provide access to their mail using any IMAP4 mail client, including WinPMail.  The problem is that the road warriors many time cannot make a VPN connection or even connect via port 143 due to firewall restrictions.  That's why I knowmally add a webmail server running via IMAP4 to Mercury/32.  In this case you have port 80 open connecting to your webserver.  I like SquirrelMail, it's easy and free.


 

[quote user="Joerg"]<p>Dear Thomas,</p><p>Thanks for your quick reply. But why you need an additional email client like SquirrelMail when accessing via webmail by browser?</p><p>Does Mercury grant web access. Which Mercury module has this functionality?</p><p>regards</p><p>Joerg </p><p>[/quote]</p><p>MercuryI provides IMAP4 access to any IMAP4 mail client via port 143.  If the users are coming in via a VPN connection then this should be all that is required to provide access to their mail using any IMAP4 mail client, including WinPMail.  The problem is that the road warriors many time cannot make a VPN connection or even connect via port 143 due to firewall restrictions.  That's why I knowmally add a webmail server running via IMAP4 to Mercury/32.  In this case you have port 80 open connecting to your webserver.  I like SquirrelMail, it's easy and free.</p><p>  </p>

Dear Thomas,

Now I'm at home and just seen your reply. And now I've understood. Quirrel is an email web server which has to be installed on server side within the LAN and not on client side. But this is not necessary for us because we use OpenVPN. OpenVPN can operate via Port 80 to get a connection through Firewalls. But good to know other solutions.

Now I will test the Mercury I module within the next days. Thanks for the moment and nice evening - oh sorry I mean nice afternoon.  :-)

 

Joerg

<P>Dear Thomas,</P> <P>Now I'm at home and just seen your reply. And now I've understood. Quirrel is an email web server which has to be installed on server side within the LAN and not on client side. But this is not necessary for us because we use OpenVPN. OpenVPN can operate via Port 80 to get a connection through Firewalls. But good to know other solutions.</P> <P>Now I will test the Mercury I module within the next days. Thanks for the moment and nice evening - oh sorry I mean nice afternoon.  :-)</P> <P mce_keep="true"> </P> <P>Joerg</P>

[quote user="Joerg"]

Is it possible to simultaneously access to an user mailbox by IMAP4 from remote and by PMail from local LAN?

[/quote]

This is a bad idea, you will probably get corrupted folders.

2 (or more) x IMAP is OK, but keep Pegasus (in file access mode) away from the files if there is any other access happening.

Set up an IMAP profile in Pegasus for any users that this will be a problem for. 

 

[quote user="Joerg"]<p> Is it possible to simultaneously access to an user mailbox by IMAP4 from remote and by PMail from local LAN?</p><p>[/quote]</p><p>This is a bad idea, you will probably get corrupted folders.</p><p>2 (or more) x IMAP is OK, but keep Pegasus (in file access mode) away from the files if there is any other access happening. </p><p>Set up an IMAP profile in Pegasus for any users that this will be a problem for. </p><p> </p>

I thought as much that it maybe produce problems when simultaneously accessing via Pegasus (local) and IMAP from remote. But is it possible in general to access via Pegasus (file access mode) and Pegasus IMAP one after another, that means not simultaneously? Or does Pegasus change any folder structures or files each time when accessing by different protocols?

The other problem is, that nearly each office user is able to check the mailbox of the other colleques in case of vacation or sickness by his own Pegasus Client. Avoiding problems now I should change ALL Pegasus Clients to IMAP although they are situated locally. And that's only for a remote access of some street warriors. Is there any better solution available without changing all Pegasus Clients to IMAP?

 

greetings

 

Joerg 

<p>I thought as much that it maybe produce problems when simultaneously accessing via Pegasus (local) and IMAP from remote. But is it possible in general to access via Pegasus (file access mode) and Pegasus IMAP one after another, that means not simultaneously? Or does Pegasus change any folder structures or files each time when accessing by different protocols?</p><p>The other problem is, that nearly each office user is able to check the mailbox of the other colleques in case of vacation or sickness by his own Pegasus Client. Avoiding problems now I should change ALL Pegasus Clients to IMAP although they are situated locally. And that's only for a remote access of some street warriors. Is there any better solution available without changing all Pegasus Clients to IMAP?</p><p> </p><p>greetings</p><p> </p><p>Joerg </p>

[quote user="Joerg"]

I thought as much that it maybe produce problems when simultaneously accessing via Pegasus (local) and IMAP from remote. But is it possible in general to access via Pegasus (file access mode) and Pegasus IMAP one after another, that means not simultaneously? Or does Pegasus change any folder structures or files each time when accessing by different protocols?

The other problem is, that nearly each office user is able to check the mailbox of the other colleques in case of vacation or sickness by his own Pegasus Client. Avoiding problems now I should change ALL Pegasus Clients to IMAP although they are situated locally. And that's only for a remote access of some street warriors. Is there any better solution available without changing all Pegasus Clients to IMAP?

greetings

Joerg 

[/quote]

I would not convert all Pegasus mail to IMAP4.  First of all if Pegasus Mail is being used in the direct mode it's a lot faster and easier to use.  Second there is a lock file setup by both MercuryI and Pegasus Mail to let people know that they may be trying to use both at the same time.  The only problem that could occur is that some other user is accessing your mailbox either via "Add mailbox to list" or IMAP4 and you end up working the same folders at the same time.   In fact you cannot connect via IMAP4 if Pegasus Mail's lock file is in place.  As long as you take a bit of care to exit Pegasus Mail when leaving a workstation before trying to access from another location this should not be a problem.

 

That said, personally I find myself coming into the server via FTP all the time to delete the lock file so i can access the account via IMAP4.  ;-(

 

 

 

[quote user="Joerg"]<p>I thought as much that it maybe produce problems when simultaneously accessing via Pegasus (local) and IMAP from remote. But is it possible in general to access via Pegasus (file access mode) and Pegasus IMAP one after another, that means not simultaneously? Or does Pegasus change any folder structures or files each time when accessing by different protocols?</p><p>The other problem is, that nearly each office user is able to check the mailbox of the other colleques in case of vacation or sickness by his own Pegasus Client. Avoiding problems now I should change ALL Pegasus Clients to IMAP although they are situated locally. And that's only for a remote access of some street warriors. Is there any better solution available without changing all Pegasus Clients to IMAP? </p><p>greetings</p><p>Joerg </p><p>[/quote]</p><p>I would not convert all Pegasus mail to IMAP4.  First of all if Pegasus Mail is being used in the direct mode it's a lot faster and easier to use.  Second there is a lock file setup by both MercuryI and Pegasus Mail to let people know that they may be trying to use both at the same time.  The only problem that could occur is that some other user is accessing your mailbox either via "Add mailbox to list" or IMAP4 and you end up working the same folders at the same time.   In fact you cannot connect via IMAP4 if Pegasus Mail's lock file is in place.  As long as you take a bit of care to exit Pegasus Mail when leaving a workstation before trying to access from another location this should not be a problem.</p><p> </p><p>That said, personally I find myself coming into the server via FTP all the time to delete the lock file so i can access the account via IMAP4.  ;-(</p><p> </p><p> </p><p> </p>

Hi Thomas,

>  Second there is a lock file setup by both MercuryI and Pegasus Mail.

Where I can find much more information about the lock file setup you descibed? I Have already searched the whole Mercury Manual for it. 

<p>Hi Thomas,</p><p>>  Second there is a lock file setup by both MercuryI and Pegasus Mail.</p><p>Where I can find much more information about the lock file setup you descibed? I Have already searched the whole Mercury Manual for it. </p>

Hi Thomas,

>  Second there is a lock file setup by both MercuryI and Pegasus Mail.

Where

I can find much more information about the lock file setup you

descibed? I Have already searched the whole Mercury Manual for it.

<p>Hi Thomas,</p><p>>  Second there is a lock file setup by both MercuryI and Pegasus Mail.</p><p>Where I can find much more information about the lock file setup you descibed? I Have already searched the whole Mercury Manual for it. </p>

There are two lock files, one created by MercuryI and one created by WinPMail.   

  • Pegasus Mail creates a file called MAILBOXP.LCK on startup and deletes it on normal shutdown. If there is a crash the file remains and you'll get the query on startup.  You'll also get the warning if it finds a MAILBOXM.LCK in the mail directory on startup.  You can bypass this lock but you have been warned that there may be someone else working the same mailbox.
  • MercuryI creates a file called MAILBOXM.LCK when the IMAP4 user logs in and deletes it on logout.  If the MAILBOXP.LCK file is in place then the IMAP4 login fails, it cannot be bypassed. 
<p>There are two lock files, one created by MercuryI and one created by WinPMail.   </p><ul><li>Pegasus Mail creates a file called MAILBOXP.LCK on startup and deletes it on normal shutdown. If there is a crash the file remains and you'll get the query on startup.  You'll also get the warning if it finds a MAILBOXM.LCK in the mail directory on startup.  You can bypass this lock but you have been warned that there may be someone else working the same mailbox.</li><li>MercuryI creates a file called MAILBOXM.LCK when the IMAP4 user logs in and deletes it on logout.  If the MAILBOXP.LCK file is in place then the IMAP4 login fails, it cannot be bypassed.  </li></ul>

Hi Thomas,

I know this query. Always when Pegasus has been finished not correctly this query appears on re-start. Now I understand where it comes from. When an access via IMAP is denied because of an existing Pegasus Lock file, then this is exactly the solution I need. I will test it within the next days. Thanks for your help.

<p>Hi Thomas,</p><p>I know this query. Always when Pegasus has been finished not correctly this query appears on re-start. Now I understand where it comes from. When an access via IMAP is denied because of an existing Pegasus Lock file, then this is exactly the solution I need. I will test it within the next days. Thanks for your help. </p>

Hi Thomas,

 

In the meantime I have additionally activated the IMAP Server in Mercury/32 and also an access by Pegasus via IMAP from remote could be established. But for any outgoing emails, Pegasus uses the local configuration, that means it uses the SMTP server definition from my ISP at home. Is it possible to configure Pegasus in that manner, that whenever I'm connected via IMAP to my remote mailbox, Pegasus sends all outgoing email not via myprivat SMTP server but via the Mercury SMTP Relay Client, which is activ and used by all office Pegasus clients?

 

greetings

 

Joerg 

<p>Hi Thomas,</p><p> </p><p>In the meantime I have additionally activated the IMAP Server in Mercury/32 and also an access by Pegasus via IMAP from remote could be established. But for any outgoing emails, Pegasus uses the local configuration, that means it uses the SMTP server definition from my ISP at home. Is it possible to configure Pegasus in that manner, that whenever I'm connected via IMAP to my remote mailbox, Pegasus sends all outgoing email not via myprivat SMTP server but via the Mercury SMTP Relay Client, which is activ and used by all office Pegasus clients?</p><p> </p><p>greetings</p><p> </p><p>Joerg </p>

[quote user="Joerg"]

Hi Thomas,

 

In the meantime I have additionally activated the IMAP Server in Mercury/32 and also an access by Pegasus via IMAP from remote could be established. But for any outgoing emails, Pegasus uses the local configuration, that means it uses the SMTP server definition from my ISP at home. Is it possible to configure Pegasus in that manner, that whenever I'm connected via IMAP to my remote mailbox, Pegasus sends all outgoing email not via myprivat SMTP server but via the Mercury SMTP Relay Client, which is activ and used by all office Pegasus clients?

greetings

Joerg 

[/quote]

Create an identity for use with your IMAP4 folder, become that identity and then setup the Tools | Internet options for that identity.  You need to enter the general and SMTP info.  You then attach that identity to the IMAP4 folder(s). Now when replying or forwarding mail in these folders it will use this identity and SMTP host.

 

[quote user="Joerg"]<p>Hi Thomas,</p><p> </p><p>In the meantime I have additionally activated the IMAP Server in Mercury/32 and also an access by Pegasus via IMAP from remote could be established. But for any outgoing emails, Pegasus uses the local configuration, that means it uses the SMTP server definition from my ISP at home. Is it possible to configure Pegasus in that manner, that whenever I'm connected via IMAP to my remote mailbox, Pegasus sends all outgoing email not via myprivat SMTP server but via the Mercury SMTP Relay Client, which is activ and used by all office Pegasus clients?</p><p>greetings</p><p>Joerg </p><p>[/quote]</p><p>Create an identity for use with your IMAP4 folder, become that identity and then setup the Tools | Internet options for that identity.  You need to enter the general and SMTP info.  You then attach that identity to the IMAP4 folder(s). Now when replying or forwarding mail in these folders it will use this identity and SMTP host.</p><p> </p>

Hello Thomas,

 

Thanks a lot for your support. I will test it. I remember for the opportunity of Identities.  -  Joerg, read the fu...ing manual.  [:$]

Just another question. We have moved our Mercury installation to a new machine. Therefore I have installed the latest Mercury edition on the new Server. Afterwards I have configuated the server to start Mercury as a new service on start-up. Then I have updated Mercury on the old server to the same release. Then I have copied the whole Mercury folder structure from the old server to the new server, overwriting the first installation. Only the drive letter, where Mercury is installed now (D:\  ->  E:\) has been changed. Therefore I have changed all paths within Mercury. All runs properly except the Help. The use of the Help Button within each dialog box or the direct call of the Help caused to nothing. Have you any ideas? The help file is available.

greetings

 
Joerg 

<p>Hello Thomas,</p><p> </p><p>Thanks a lot for your support. I will test it. I remember for the opportunity of Identities.  -  Joerg, read the fu...ing manual.  [:$] </p><p>Just another question. We have moved our Mercury installation to a new machine. Therefore I have installed the latest Mercury edition on the new Server. Afterwards I have configuated the server to start Mercury as a new service on start-up. Then I have updated Mercury on the old server to the same release. Then I have copied the whole Mercury folder structure from the old server to the new server, overwriting the first installation. Only the drive letter, where Mercury is installed now (D:\  ->  E:\) has been changed. Therefore I have changed all paths within Mercury. All runs properly except the Help. The use of the Help Button within each dialog box or the direct call of the Help caused to nothing. Have you any ideas? The help file is available. </p><p>greetings</p><p>  Joerg </p>

Just a guess, it this a vista machine?  If so you need to go to MS and get the winhelp32.exe

Just a guess, it this a vista machine?  If so you need to go to MS and get the winhelp32.exe
live preview
enter atleast 10 characters
WARNING: You mentioned %MENTIONS%, but they cannot see this message and will not be notified
Saving...
Saved
With selected deselect posts show selected posts
All posts under this topic will be deleted ?
Cancel
Delete
Pending draft ... Click to resume editing
Discard draft