I've always installed Windoze software in non-standard locations and Eudora is no exception. My Eudora 7.1 is in C:\eudor301. Copying the new QCSSL files into C:\eudor301 allowed Eudora to work just fine. Thanks a lot for this software update.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Are there additional steps that must be taken after copying the new files over? I copied the files, but Eudora is unable to connect & retrieve email from any of my 8 email providers. 3 providers refuse the connection; the rest just sit for some time until they eventually time out. I'm running on Win7 64-bit OS. Also, I'm also interested in your response to Walt's question (TLS 1.2 support).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Bill did you see the note about redownloading and installing a new version of the files?
Hello, everyone. I apologise for this—it's all my fault—but it turns out
the distribution of OpenSSL included in the new Hermes QCSSL package is badly broken. The reason it squeaked by me is that I use Linux at the moment (I am in Europe, away from my usual computers), and I can't check the version of DLL's. In the interests of quality assurance, though, I dug out a 2001-era netbook and tested everything on an actual version of
Eudora. It works now.
Please find the updated, it-works-this-time-100%-honest version at https://sourceforge.net/projects/hermesmail/files/HermSSL.zip/download.
Once again, I am deeply sorry for the repeated attempts it took to get this right, and I am especially sorry that I solicited money before we had it tested to work. That said, it works now, and very well at that.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Walt... Thanks for your response. I have MS Visual C++ 2015 version (x86 & x64) on my system (in addition to 2008, 2010 and 2012 x86/x64 versions). I downloaded the 2nd HermSSL.zip update & installed the x64 versions of the 4 files & the results are the same for all 8 email providers I have. Four of them sit there for 3-5 minutes before timing out; the other four return in less than a minute -- all with "Error reading from network". Six have cause "Connection closed by foreign host (0)"; one has cause "Cause: connection aborted due to timeout or other failure (10053)"; and one with "Cause: Eudora got tired of waiting for the server. (10100)."
All email from my 8 different providers works fine in Eudora with the previous (original) files. Guess I'll just stick with my original files & keep trusting new Gmail certificates every week.
Last edit: Bill McIntyre 2018-09-08
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Uh... "removing them both"... not sure what you're referring to. The MS Visual C++ install? BTW, I've tried the updated HermSSL.zip files on another Win 7 (64-bit) laptop and it behaves exactly the same way as the first one. Eudora config is the same on both systems. Same "Error reading from network" from all email providers. I also have several WinXP (32-bit) systems with same Eudora files & setup, but I haven't tried the HermSSL.zip files on them yet. Wasn't sure if the new QCSSL.dll (& other dll's) were compatible with WinXP.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I meant removing the C++ redistributables and trying them one at the time.
It's one of those advices along the line of: Have you tried to reboot?
I wasn't proud of it, but I suggested it anyway. I call it the "Engineer's
solution". Which roughly translates to "Hitting it with a wrench and see if
that helps."
Uh... "removing them both"... not sure what you're referring to. The MS
Visual C++ install? BTW, I've tried the updated HermSSL.zip files on
another Win 7 (64-bit) laptop and it behaves exactly the same way as the
first one. Eudora config is the same on both systems. Same "Error reading
from network" from all email providers. I also have several WinXP (32-bit)
systems with same Eudora files & setup, but I haven't tried the HermSSL.zip
files on them yet. Wasn't sure if the new QCSSL.dll (& other dll's) were
compatible with WinXP.
Thanks for the clarification! My most recent desktop is 2 yrs old (Dell XPS 8900) & also has Windows 7 (64-bit) and same Eudora 7.1.0.9 files & configuration. It didn't have MS Visual C++ 2015 installed, so I installed the x86 version (v14.0.24123); copied the four x86 Hermes files; and started up Eudora. I get the same results as on my two Win7 laptops (Error reading from network). Can't connect to any of my 8 email hosts.
I then closed Eudora; installed MS Visual C++ 2015 x64 version; copied the four x64 Hermes files to the Eudora folder; & started up Eudora. Same results - can't connect to any of my email providers (Error reading from network). Six of the eight email hosts list cause as "Connection closed by foreign host (0)" for both x86 & x64 files.
Am I one of the few (or only) outliers that have been unable to get this to work? If so, I have to assume the problem must be on my end. Eudora works great on my four Win7 systems & four WinXP systems, sending & retrieving 23 different email addresses from 8 email hosts. The only issue is having to trust incoming & outgoing Gmail certificates every week on all eight systems. I'm more worried about whether or not my current Eudora setup will still work if email providers stop supporting TLS v1. Do your updates support TLS v1.2 or greater?
Thanks again for your assistance.
Bill
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm not a a network expert, and for strange reasons I don't have access to
that particular library source code.
But it sounds, on the face of it, like a protocol or connection negotiation
problem. Why it hits you and not others is a mystery I can't answer.
There must be something different between the ones that work and those who
doesn't (Man, my deductive powers are running amok here :P), but yes,
identifying that difference is probably the proverbial needle in a
haystack.
Wasn't it Pete Maclean who wrote (or finished) the library? He must have a
better idea than me.
Thanks for the clarification! My most recent desktop is 2 yrs old (Dell
XPS 8900) & also has Windows 7 (64-bit) and same Eudora 7.1.0.9 files &
configuration. It didn't have MS Visual C++ 2015 installed, so I installed
the x86 version (v14.0.24123); copied the four x86 Hermes files; and
started up Eudora. I get the same results as on my two Win7 laptops (Error
reading from network). Can't connect to any of my 8 email hosts.
I then closed Eudora; installed MS Visual C++ 2015 x64 version; copied the
four x64 Hermes files to the Eudora folder; & started up Eudora. Same
results - can't connect to any of my email providers (Error reading from
network). Six of the eight email hosts list cause as "Connection closed by
foreign host (0)" for both x86 & x64 files.
Am I one of the few (or only) outliers that have been unable to get this
to work? If so, I have to assume the problem must be on my end. Eudora
works great on my four Win7 systems & four WinXP systems, sending &
retrieving 23 different email addresses from 8 email hosts. The only issue
is having to trust incoming & outgoing Gmail certificates every week on all
eight systems. I'm more worried about whether or not my current Eudora
setup will still work if email providers stop supporting TLS v1. Do your
updates support TLS v1.2 or greater?
Oh. I forgot. I actually have the code, the project file is just missing.
Can't do anything about that until I'm home though.
Regards
I'm not a a network expert, and for strange reasons I don't have access to
that particular library source code.
But it sounds, on the face of it, like a protocol or connection
negotiation problem. Why it hits you and not others is a mystery I can't
answer.
There must be something different between the ones that work and those who
doesn't (Man, my deductive powers are running amok here :P), but yes,
identifying that difference is probably the proverbial needle in a
haystack.
Wasn't it Pete Maclean who wrote (or finished) the library? He must have a
better idea than me.
Thanks for the clarification! My most recent desktop is 2 yrs old (Dell
XPS 8900) & also has Windows 7 (64-bit) and same Eudora 7.1.0.9 files &
configuration. It didn't have MS Visual C++ 2015 installed, so I installed
the x86 version (v14.0.24123); copied the four x86 Hermes files; and
started up Eudora. I get the same results as on my two Win7 laptops (Error
reading from network). Can't connect to any of my 8 email hosts.
I then closed Eudora; installed MS Visual C++ 2015 x64 version; copied
the four x64 Hermes files to the Eudora folder; & started up Eudora. Same
results - can't connect to any of my email providers (Error reading from
network). Six of the eight email hosts list cause as "Connection closed by
foreign host (0)" for both x86 & x64 files.
Am I one of the few (or only) outliers that have been unable to get this
to work? If so, I have to assume the problem must be on my end. Eudora
works great on my four Win7 systems & four WinXP systems, sending &
retrieving 23 different email addresses from 8 email hosts. The only issue
is having to trust incoming & outgoing Gmail certificates every week on all
eight systems. I'm more worried about whether or not my current Eudora
setup will still work if email providers stop supporting TLS v1. Do your
updates support TLS v1.2 or greater?
Thanks for the clarification! My most recent desktop is 2 yrs old (Dell
XPS 8900) & also has Windows 7 (64-bit) and same Eudora 7.1.0.9 files &
configuration. It didn't have MS Visual C++ 2015 installed, so I installed
the x86 version (v14.0.24123); copied the four x86 Hermes files; and
started up Eudora. I get the same results as on my two Win7 laptops (Error
reading from network). Can't connect to any of my 8 email hosts.
I then closed Eudora; installed MS Visual C++ 2015 x64 version; copied the
four x64 Hermes files to the Eudora folder; & started up Eudora. Same
results - can't connect to any of my email providers (Error reading from
network). Six of the eight email hosts list cause as "Connection closed by
foreign host (0)" for both x86 & x64 files.
Am I one of the few (or only) outliers that have been unable to get this
to work? If so, I have to assume the problem must be on my end. Eudora
works great on my four Win7 systems & four WinXP systems, sending &
retrieving 23 different email addresses from 8 email hosts. The only issue
is having to trust incoming & outgoing Gmail certificates every week on all
eight systems. I'm more worried about whether or not my current Eudora
setup will still work if email providers stop supporting TLS v1. Do your
updates support TLS v1.2 or greater?
The original HermSSL.zip that was posted 3 days ago was seriously broken. The OpenSSL DLLs that it contained were 12 years old and totally incompatible with the QCSSL DLL.
The updated HermSSL.zip that was posted later is seriously broken. Its OpenSSL DLLs are of an appropriate version but are dependent on another DLL ("LIBEAY32MD.DLL") that was not included. This missing DLL should not be part of the package anyway and probably means that these files come from a debug build that should not be distributed.
As of the moment of this writing, these packages have been downloaded 70 times. And they will not work for anyone.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Just tried the updated HermSSL.zip files on my Win7 desktop & they appear to work perfectly! No issues whatsoever! Mucho Thanks!!! I'll try it on my XP systems later this evening & will let you know how that goes. Thanks to all (i.e. Nick, Walt, Soren, Pete) for your efforts & recommendations! While having to retrust Gmail certificates every week was an inconvenience, it certainly wasn't a showstopper. I'm more concerned about Eudora's TLSv1. I'm a member of a torrent site, and they're dropping support for TLSv1 & TLSv1.1 this November. I'm just afraid that some (or all) email providers will start dropping support for TLSv1, which would break Eudora, right?
Anywho's... KUDOS for all your efforts to date & keep up the great work! BTW, since my programming skills are rather out of date, I'll gladly volunteer to be a alpha/beta tester for you. I have four Win7 (64bit) systems and four XP (32bit) systems, all with the exact same Eudora 7.1.0 9 files & configuration, that I can test anything on.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thank you for the kudos! Now I have started such productive work on QCSSL, I intend to continue with it. The next thing I would like to do is to remove its dependence on the Microsoft Visual C++ redistributables but I have been looking into that today and concluded that it is not going to be easy. Other things I would like to do include adding support for TLS 1.3 (which is easy), removing support for SSL 2.0 and other obsoleted technologies, and improving troubleshooting facilities. And thank you also for volunteering as a tester. Let's do at least one round of closed beta-testing in future before distributing updates more widely.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Much as though continuing work on QCSSL is a worthwhile endeavour, it does work now, with SSL 1.3 to boot, so you might consider concurrently working either on spellcheck or the HTML engine. I sent you an eMail earlier—not sure if you read it—but there is a snap-in framework version of Blink called the Chromium Embedded Framework. If I understand correctly, the only thing needed in this instance is to replace references to Trident with references to the Chromium Embedded Framework. It should be much easier than trying to adapt Gecko.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I agree that continued work on QCSSL does not merit high priority. There is a temptation to keep going with it because of the momentum I have built up but I can restrain myself!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
No, by all means, please do go ahead. Let's make QCSSL the best SSL toolkit it can be. As long as someone works on the HTML engine and on giving Stingray the heave ho, we'll be fine. We're not working to a deadline or anything, though I'd like to have a compiled version by Feb. (ideally by Jan.)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
In my earlier reply, I neglected to address your question about dropping support for TLS 1.0. And you are correct, anyone using "pure" Eudora and relying on TLS would be stuck if their email provider stopped supporting TLS 1.0.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Does this version just provide support for current certificates OR is there more, such as TLS 1.2 support? TIA
Walt
This version supports TLS 1,0, 1.1 and 1.2. It does not support 1.3 but that will come soon.
Pete
Thanks for the info update, Pete.
I've always installed Windoze software in non-standard locations and Eudora is no exception. My Eudora 7.1 is in C:\eudor301. Copying the new QCSSL files into C:\eudor301 allowed Eudora to work just fine. Thanks a lot for this software update.
Are there additional steps that must be taken after copying the new files over? I copied the files, but Eudora is unable to connect & retrieve email from any of my 8 email providers. 3 providers refuse the connection; the rest just sit for some time until they eventually time out. I'm running on Win7 64-bit OS. Also, I'm also interested in your response to Walt's question (TLS 1.2 support).
Bill did you see the note about redownloading and installing a new version of the files?
Hello, everyone. I apologise for this—it's all my fault—but it turns out
the distribution of OpenSSL included in the new Hermes QCSSL package is badly broken. The reason it squeaked by me is that I use Linux at the moment (I am in Europe, away from my usual computers), and I can't check the version of DLL's. In the interests of quality assurance, though, I dug out a 2001-era netbook and tested everything on an actual version of
Eudora. It works now.
Please find the updated, it-works-this-time-100%-honest version at
https://sourceforge.net/projects/hermesmail/files/HermSSL.zip/download.
Once again, I am deeply sorry for the repeated attempts it took to get this right, and I am especially sorry that I solicited money before we had it tested to work. That said, it works now, and very well at that.
Bill.....please go into Control Panel/uninstall programs and check your version of MS Visual C++....it needs to be the 2015 version.
If it's not, you can download it here: https://www.microsoft.com/en-us/download/details.aspx?id=52685
Hi Walt... Thanks for your response. I have MS Visual C++ 2015 version (x86 & x64) on my system (in addition to 2008, 2010 and 2012 x86/x64 versions). I downloaded the 2nd HermSSL.zip update & installed the x64 versions of the 4 files & the results are the same for all 8 email providers I have. Four of them sit there for 3-5 minutes before timing out; the other four return in less than a minute -- all with "Error reading from network". Six have cause "Connection closed by foreign host (0)"; one has cause "Cause: connection aborted due to timeout or other failure (10053)"; and one with "Cause: Eudora got tired of waiting for the server. (10100)."
All email from my 8 different providers works fine in Eudora with the previous (original) files. Guess I'll just stick with my original files & keep trusting new Gmail certificates every week.
Last edit: Bill McIntyre 2018-09-08
OK.....obviously still a problem here of some kind.
Just my 2 bits... Have you tried removing them both, then installing them
one at a time? Trying one at the time, preferably the newest first.
Regards
On Saturday, September 8, 2018, Walt Stagner wstagner@users.sourceforge.net
wrote:
--
Søren Bro Thygesen
I know it sounds like banality, but sometimes the "engineers solution"
(Hitting stuff hard with a wrench) does actually work.
Out forefathers started out hitting stuff with a heavy stick.
Nowadays we punch to lead-ions together in an extremely complicated
machine. But the point is basically the same.
:)
Regards.
On Sat, Sep 8, 2018 at 6:05 PM Soren Bro sbrothy@users.sourceforge.net
wrote:
Uh... "removing them both"... not sure what you're referring to. The MS Visual C++ install? BTW, I've tried the updated HermSSL.zip files on another Win 7 (64-bit) laptop and it behaves exactly the same way as the first one. Eudora config is the same on both systems. Same "Error reading from network" from all email providers. I also have several WinXP (32-bit) systems with same Eudora files & setup, but I haven't tried the HermSSL.zip files on them yet. Wasn't sure if the new QCSSL.dll (& other dll's) were compatible with WinXP.
I meant removing the C++ redistributables and trying them one at the time.
It's one of those advices along the line of: Have you tried to reboot?
I wasn't proud of it, but I suggested it anyway. I call it the "Engineer's
solution". Which roughly translates to "Hitting it with a wrench and see if
that helps."
By all means ignore me. :)
Regards.
On Sat, Sep 8, 2018 at 8:10 PM Bill McIntyre dawog@users.sourceforge.net
wrote:
Hi Soren...
Thanks for the clarification! My most recent desktop is 2 yrs old (Dell XPS 8900) & also has Windows 7 (64-bit) and same Eudora 7.1.0.9 files & configuration. It didn't have MS Visual C++ 2015 installed, so I installed the x86 version (v14.0.24123); copied the four x86 Hermes files; and started up Eudora. I get the same results as on my two Win7 laptops (Error reading from network). Can't connect to any of my 8 email hosts.
I then closed Eudora; installed MS Visual C++ 2015 x64 version; copied the four x64 Hermes files to the Eudora folder; & started up Eudora. Same results - can't connect to any of my email providers (Error reading from network). Six of the eight email hosts list cause as "Connection closed by foreign host (0)" for both x86 & x64 files.
Am I one of the few (or only) outliers that have been unable to get this to work? If so, I have to assume the problem must be on my end. Eudora works great on my four Win7 systems & four WinXP systems, sending & retrieving 23 different email addresses from 8 email hosts. The only issue is having to trust incoming & outgoing Gmail certificates every week on all eight systems. I'm more worried about whether or not my current Eudora setup will still work if email providers stop supporting TLS v1. Do your updates support TLS v1.2 or greater?
Thanks again for your assistance.
Bill
(AFK)
I'm not a a network expert, and for strange reasons I don't have access to
that particular library source code.
But it sounds, on the face of it, like a protocol or connection negotiation
problem. Why it hits you and not others is a mystery I can't answer.
There must be something different between the ones that work and those who
doesn't (Man, my deductive powers are running amok here :P), but yes,
identifying that difference is probably the proverbial needle in a
haystack.
Wasn't it Pete Maclean who wrote (or finished) the library? He must have a
better idea than me.
Regards
On Sunday, September 9, 2018, Bill McIntyre dawog@users.sourceforge.net
wrote:
--
Søren Bro Thygesen
Oh. I forgot. I actually have the code, the project file is just missing.
Can't do anything about that until I'm home though.
Regards
I'm not a a network expert, and for strange reasons I don't have access to
--
Søren Bro Thygesen
I received the project file for that particular project. From reading the
XML I can see that the target platform is Windows 8.1?
I have trouble, though, seeing why it would work on som Win7 machines and
not others just because of that.
I still haven't been into the code though.
About TLS 1.2 I guess we will have to.
What I can see very vividly though, is that we need to get to work....
I'm still fairly new to the project though, so don't take me too seriously.
I was hoping someone would have stepped in by now.
Regards
On Sunday, September 9, 2018, Bill McIntyre dawog@users.sourceforge.net
wrote:
--
Søren Bro Thygesen
I have not tested the new QCSSL.dll with Windows XP but I believe it is compatible. Certainly I have not done anything to render it incompatible.
The original HermSSL.zip that was posted 3 days ago was seriously broken. The OpenSSL DLLs that it contained were 12 years old and totally incompatible with the QCSSL DLL.
The updated HermSSL.zip that was posted later is seriously broken. Its OpenSSL DLLs are of an appropriate version but are dependent on another DLL ("LIBEAY32MD.DLL") that was not included. This missing DLL should not be part of the package anyway and probably means that these files come from a debug build that should not be distributed.
As of the moment of this writing, these packages have been downloaded 70 times. And they will not work for anyone.
Just tried the updated HermSSL.zip files on my Win7 desktop & they appear to work perfectly! No issues whatsoever! Mucho Thanks!!! I'll try it on my XP systems later this evening & will let you know how that goes. Thanks to all (i.e. Nick, Walt, Soren, Pete) for your efforts & recommendations! While having to retrust Gmail certificates every week was an inconvenience, it certainly wasn't a showstopper. I'm more concerned about Eudora's TLSv1. I'm a member of a torrent site, and they're dropping support for TLSv1 & TLSv1.1 this November. I'm just afraid that some (or all) email providers will start dropping support for TLSv1, which would break Eudora, right?
Anywho's... KUDOS for all your efforts to date & keep up the great work! BTW, since my programming skills are rather out of date, I'll gladly volunteer to be a alpha/beta tester for you. I have four Win7 (64bit) systems and four XP (32bit) systems, all with the exact same Eudora 7.1.0 9 files & configuration, that I can test anything on.
Thank you for the kudos! Now I have started such productive work on QCSSL, I intend to continue with it. The next thing I would like to do is to remove its dependence on the Microsoft Visual C++ redistributables but I have been looking into that today and concluded that it is not going to be easy. Other things I would like to do include adding support for TLS 1.3 (which is easy), removing support for SSL 2.0 and other obsoleted technologies, and improving troubleshooting facilities. And thank you also for volunteering as a tester. Let's do at least one round of closed beta-testing in future before distributing updates more widely.
Much as though continuing work on QCSSL is a worthwhile endeavour, it does work now, with SSL 1.3 to boot, so you might consider concurrently working either on spellcheck or the HTML engine. I sent you an eMail earlier—not sure if you read it—but there is a snap-in framework version of Blink called the Chromium Embedded Framework. If I understand correctly, the only thing needed in this instance is to replace references to Trident with references to the Chromium Embedded Framework. It should be much easier than trying to adapt Gecko.
I agree that continued work on QCSSL does not merit high priority. There is a temptation to keep going with it because of the momentum I have built up but I can restrain myself!
No, by all means, please do go ahead. Let's make QCSSL the best SSL toolkit it can be. As long as someone works on the HTML engine and on giving Stingray the heave ho, we'll be fine. We're not working to a deadline or anything, though I'd like to have a compiled version by Feb. (ideally by Jan.)
In my earlier reply, I neglected to address your question about dropping support for TLS 1.0. And you are correct, anyone using "pure" Eudora and relying on TLS would be stuck if their email provider stopped supporting TLS 1.0.