I am running the 64 bit version of Win7.  I have an XP system that I can use for a test platform.  I'll try that.

I don't see any options for encryption key length when generating self-signed certs within Mercury32.  The service I see running on Win7 is called "Cryptographic Services" and I can't tell if that's using the crypt dlls or not.

 I'll post back after I test on XP.  I appreciate all the help.

Hi Folks, I've been a Mercury32 user for years on a local net and now want to add POP3 for remote users.  Trying to implement SSL and I'm getting the following error reported in session logging:

 20: Error -3 creating CryptLib session.

 I've read through the manual, activated SSL in the POP3 server config, generated the self-signed certificate, etc. 

I'm running the 4.74 release of Mercury32 and the latest Thunderbird client.  Using STARTTLS via port 110.  No firewall issue that I can see.

 Any suggestions?

There are some compatibility issues with Cryptlib, and it could be that the current Thunderbird release simply won't work with it. The upcoming v4.80 release of Mercury, that is being beta tested right now, will replace Cryptlib with OpenSSL.

/Rolf 

Thanks.  I'll try a different client.  I really appreciate the help.

Interestingly, I get exactly the same error with the Pegasus mail client, so I apparently have a different issue.  It's happening with both POP3 and IMAP4.

Try browsing for the certificate file from the settings dialog for each module so you get the full path, and make sure there is no firewall or antivirus software that may interfere with network access.

/Rolf 

[quote user="rshultz"]Interestingly, I get exactly the same error with the Pegasus mail client, so I apparently have a different issue.  It's happening with both POP3 and IMAP4.[/quote]

Don't use POP3 - but IMAP with SSL (Port 993) and SMTP with STARTTLS (Port 587). That works fine with different mailclients (i.e. Pegasus, Thunderbird, Outlook), but in all cases you have to manually accept the selfsigned certificate. On Thunderbird a window should pop up to download certificate and accept it. It may not pop up on first try sometimes or pops up in background.

Thanks for the help.  After working with three different email clients using the settings above I still get the following line in my session log and can't achieve a successful connection: Error -3 creating CryptLib session.  I also can't get a certificate acceptance request, so I'm at a loss.

Imap works fine until I try to implement SSL.  The cryptlib dlls are on my system, but I don't know anything about cryptlib, so I can't proceed. 

Du you get that error with self-signed certificate too? My description with accepting the certificate was for that.

I installed Mercury out of box and added nothing. Or do you mean the crypt-dlls by Microsoft in \windows\system32?

Yes, the self-signed certificate generated by Mercury is all I am working with.  In regards to the crypt dlls, I did the same and installed Mercury32 and noted that the crypt dlls are in that directory.

 I'm running the current release of Mercury under Windows 7 pro.  Not sure what to try next.  Imap runs fine with non-SSL.  When I turn on SSL the firewall shows the ports exposed.  The session logs generate when I try to connect.  I just get that cryptlib error message.  I can't get any offer to accept a certificate using Outlook, Thunderbird or Pegasus.  Not sure where to go next.

[quote user="rshultz"]I'm running the current release of Mercury under Windows 7 pro.[/quote]

Hmm - I'm running Mercury on WinXP SP3. May be this issue is with the crypt dlls of Win7? Would it be possible for you to have a test on WinXP?

Another reason may be, that in one of last patchdays Microsoft announced, that they no longer would support short RSA-Keys. Mine is 1024 bit and I'm not shure if you have the choice to assign different length of RSA-keys during creation of self signed certificate (sorry ... created that certificate a long time ago). And ... you should make an exception on Mercury Core Process in Windows firewall.

Another idea: have a look at the services of Windows. Is the crypt service running?

Olaf

Your Win7 - is it 32 or 64 bit? May be 64 bit could be a problem?