Community Discussions and Support
Let's get this party started with some v4.80 upgrade questions

Right, existing licenses are good for all v4 releases of Mercury!

There are actually a few important fixes in v4.80 final, so I would recommend to update. 

<p>Right, existing licenses are good for all v4 releases of Mercury!</p><p>There are actually a few important fixes in v4.80 final, so I would recommend to update.<span style="font-size: 10pt;"> </span></p>

1.  I have three users accessing via IMAP with a variety of devices.  Some of them have SSL turned off which has me wondering whether upgrading from v4.74 will disable their access.  Anything I need to be concerned with in that regard?

2.  I am running two instances of Mercury.  Do I upgrade each one by running the .exe twice pointing each run to one of the installation locations?

TIA

<p>1.  I have three users accessing via IMAP with a variety of devices.  Some of them have SSL turned off which has me wondering whether upgrading from v4.74 will disable their access.  Anything I need to be concerned with in that regard? </p><p>2.  I am running two instances of Mercury.  Do I upgrade each one by running the .exe twice pointing each run to one of the installation locations?</p><p>TIA </p>

1. If you enable SSL/TLS on the server Mercury will announce support for it, but it will be up to the connecting client to use it or not. Activating SSL will mean an extra level of complication, obviously. So if the certificate on the server is self-signed some clients may not like that, and if the client software isn't compatible with OpenSSL the connection may fail. In most environments it works fine though.

2. Right, you will need to run the installer twice to update both instances.

<p>1. If you enable SSL/TLS on the server Mercury will announce support for it, but it will be up to the connecting client to use it or not. Activating SSL will mean an extra level of complication, obviously. So if the certificate on the server is self-signed some clients may not like that, and if the client software isn't compatible with OpenSSL the connection may fail. In most environments it works fine though.</p><p>2. Right, you will need to run the installer twice to update both instances.</p>

Congratulations to David and the entire testing team for finishing the v4.80. Good piece of software.

Now some little questions from my side.

1. David says something about the new licence prices. We are already holding a 15 user licence for Mercury/32 and taking for granted this licence covers all v4.** versions of Mercury. Only when the new v5.** version is being published we have to purchase a new licence, isn't it?

2.  We have already running the beta version v4.80.119 of Dec, 10th. This version is very stable and we are happy so far. Makes it sense to update to final release v.4.80?

Greetings

Joerg

<p>Congratulations to David and the entire testing team for finishing the v4.80. Good piece of software.</p><p>Now some little questions from my side.</p><p>1. David says something about the new licence prices. We are already holding a 15 user licence for Mercury/32 and taking for granted this licence covers all v4.** versions of Mercury. Only when the new v5.** version is being published we have to purchase a new licence, isn't it?</p><p>2.  We have already running the beta version v4.80.119 of Dec, 10th. This version is very stable and we are happy so far. Makes it sense to update to final release v.4.80?</p><p>Greetings</p><p>Joerg </p>
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