Post by Piethttps://sourceforge.net/projects/hermesmail/files/ shows
a last update July 25 for the SSL package.
Pretty odd that it works fine under Win10, but not under Win8.1.
Under Win 8.1, after replacing the files in the Eudora program
dir (x86) and starting Eudora, it sits there trying to connect
to the mail servers, until it ends with 'tired of waiting'.
The showstoppers apparently are QCSSL.dll and rootcerts.p7b
Puzzled...
Found. And baffled.
I have a "special" Eudora setup:
I have 3 pc's: a fast one with Win10, a slow one with Win8.1 and
an oldie running Win7. On all of them I've installed Eudora, and
on all of them my Eudora profile is not in the default place, but
in a folder under my homedir. The Win10 pc acts as server for the
other two. On all pc's the paths to my Eudora profile are identical.
The only exception is that each pc has it's own eudora .ini file.
On each pc I start Eudora with "eudora.exe profile_path\pcname.ini"
(which of course is shorthand for the real command). I've had this
setup for 10 years or more (initially with a Win7 "main" pc,later
a new Win10 pc). It has always worked like a charm.
Now, on the Win10 pc I installed the hermes ssh files. That solved
a recent ssl-related problem with one mail server.
Then I installed the files on the Win8.1 pc. And there things went
wrong, as described.
To see what the heck was going on I fired up my heavy artillery:
wireshark. As soon as I started 'check mail' in Eudora, I noticed
frantic activity between client and server, like a zillion times
opening and closing the .ini file. This activity lasted so long
that Eudora timed out before it could connect to the mail servers.
Then I put the original QCSSL.dll and rootcerts.p7b back in place
and things were back to normal (including of course the the problem
with one server).
I now suspect that the new ssl *local* to Eudora interferes with
Windows' normal file sharing method. Next thing of course is to
find a way to circumvent this.
-p