Hi Joerg,

I know about 4.8 and I can't wait to get it. My problem here is that I cannot switch back to a plain connection due to some dependencies on the provider side and also regarding security policies within our company. And a Mercury crash always causes unexpected behavior for regarding the users IMAP mailboxes and so on :-(

Konrad

Some days ago our internet provider and hoster "1 & 1" (Germany) announced that from the beginning 2014 all e-mail transfer will be processed via SSL/TLS (for IMAP over port 993 and for POP3 over port 995) and via STARTTLS (for SMTP over port 587) only. That means the standard connections via port 25 and 110 are being closed.

I remember that a lot of issues were discussed here regarding SSL/TLS issues in past. Presently we are using Mercury 4.74. What is the current state of the SSL/TLS implementation? Has anybody experiences with long term using of these connection settings?

I remember also that David himself recommended in past to disable SSL encryption.

Presently I have switched the SMTP Client (Mercury C) to Port 587 and "SSL Encryption via STARTTLS Command". It works for the moment. Further I have changed one account of the POP3 Client (Mercury D) port 995 with "SSL Encryption using direct connection" because "SSL Encryption using STLS command" doesnt work.

Cheers

Joerg

Mercury v4.80 has OpenSSL, which will handle SSL much better than the old CryptLib routines. There is still one elusive bug to track down (not related to SSL), but it should be ready for release soon.

I didn't have any problems with SSL/TLS (even with selfsigned certificate) on Mercury yet.

But - I asume the SSL implementation in Mercury is very similar to that one in Pegasus. Pegasus won't support SSL V3 at the moment. That would not realy be a problem, if the providers would continue to support SSL V2 as fallback. But some providers force their customers to use SSL V3, but don't communicate this massive change in policy. Like german provider Strato they only communicate to force SSL - but not the version.

Hopefully David will be able to release new Mercury and Pegasus very soon!

bye    Olaf

[quote user="Rolf Lindby"]Mercury v4.80 has OpenSSL, which will handle SSL much better than the old CryptLib routines. There is still one elusive bug to track down (not related to SSL), but it should be ready for release soon.[/quote]

Hi Rolf, 

Any chance of an update on everything regarding the next update, especially potential release dates, upgrade paths etc.

I really need to get using SSL with mail and frankly the current Mercury is not fulfilling requirements with regards to compatibility for all my clients.

Anything we should be getting excited about ?

Cheers,

Dougie.

The beta testing process for Mercury 4.80 has been unusually long due to the big changes with SSL and networking in general - we are now running beta version 12 since yesterday! So far everything looks fine with this version, so I hope this is the last test before release. The updating procedure should be simple, the program is compatible with current deamons and file formats. As it's a minor release it's included in existing licenses.

And yes, I do feel a bit excited by it! It's not version 5, but it's a significant step towards it! :) 

Hi Guys,

Just for information. I have changed the SMTP settings in Mercury (Mercury C) about 3 weeks ago from Port 25 without encryption to Port 587 with SSL / STARTTLS encryption. This was necessary bacause of our e-mail provider (1&1 Germany) is going to reject any unencrypted e-mails soon. Until now it worked fine but some minutes ago Mercury C occasionally could no deliver emails. Now I have returned my settings to port 25 without encryption and it works again.

BTW, the retrieving of encrypted emails via POP3 and SSL on port 995 works fine since those 3 weeks.

Cheers

Joerg

Since yesterday (after three weeks proper running) also our POP3 connections via port 995 with "SSL encryption using direct connection" fails and let Mercury crashing different times a day.

I found the following pop_client logfile:

16:05:19.531: --- Thu Jan 09 16:05:19 2014 ---
16:05:19.531: Connect to 'pop.1und1.de:995', timeout 30.
16:05:20.703: 22: Error -10 activating SSL session (locus 6014, type 4, code 0, '')
16:05:20.703: --- Connection closed normally at Thu Jan 09 16:05:20 2014. ---

To ensure our e-mail traffic I have changed back now all pop accounts to port 110 without encryption. But I'm confused that all was running properly over weeks and now it become instable.

Hope, the intermediate solution for SSL becomes ready until our mail provider retires the support for unencrypted mail transfer.

Cheers

Joerg

Hi Guys,

Does anybody know when David will launch the announced intermediate Mercury version which better supports SSL/TLS encryption? Our provider (1&1 / Germany) has recently renewed its warning that unencrypted connection via port 25 / 110 will be rejected soon. I'm a little bit afraid that I have to retire Mercury when this happens. I have to ensure the e-mail communication in our company.

Cheers

Joerg

[quote user="Joerg"]Our provider (1&1 / Germany) has recently renewed its warning that unencrypted connection via port 25 / 110 will be rejected soon. I'm a little bit afraid that I have to retire Mercury when this happens. I have to ensure the e-mail communication in our company.

Cheers

Joerg

[/quote]

Hi,

version 4.74 is not able to send mails using SSL/TLS. Time is running

out, a new version would be appreciated.

Regards

Stefan

Hi All,

Different problem here, but related to SSL. I switched all my client pop3 account (which Mercury polls from GMX, freenet and Hotmail) to port 995 and SSL but now Mercury crashes every couple of days.

We really need the new version!

Konrad

Hi Konrad,

As descibed above, I experienced the same problems in past. Once changed to SSL, Mercury runs stable for a while. In my case about 3 weeks. But then it crashes different times a day. For the moment I have changed back the settings to ordinary unencrypted connection.

I know that David is currently testing the intermediate version 4.8 which should be released soon.

Cheers

Joerg