Pete Maclean's most recent update download contains only the three .dll files but not the rootcerts.p9b file that is referenced in his Release Notes. It appeared that the Hermes Mail download does not contain that file as well. Is it no longer necessary to install that 'certificates file' into the Eudora folder?
And thanks in advance for saving my bacon and 25 years of my email history if this Eudora update works and allows me to continue to use my old trusty program despite my ISP's new encryption requirements.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thank you so much, Pete! One last question before load the new files, if you will indulge me: your Release Notes refer to installing "rootcerts.p9b" while the file in the download is "rootcerts.p7b". My existing certificates file is "rootcerts.p7b" also.
Would I be wise to replace the three .dll's and then just replace the certificates file if I have issues? Or is there a "rootcerts.p9b" floating around there somewhere that I should use?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
My bad! Sorry. The release notes should have said "rootcerts.p7b". I have now fixed that and left a new zip to download. I suggest replacing this certificates file regardless.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Okay folks. You may not believe this, but the four files have been replced and everything appears to be working perfectly! Of course ionos.com hasn't started restricting their acceptable forms of encryption yet, but I assume this tls 1.2 will meet their requirements. I consider this one of only a handful of victories in my lifetime war against computers. Thanks very much!
Incidentally, do I need to select "If Available, STARTTLS", "Required STARTTLS", or "Required, Alternate Port" under the "Secure Sockets when Sending/Receiving" options or is the appropriate setting automatically a feature of the new files? FYI, this was done on my Windows 7 system and I intend to next move on to my computer which is running Eudora perfectly on Windows 10.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You can check in Eudora to see what the "Last SSL Info" was for the given personality and look at the "SSL Version". You should see TLSv1.2 if Eudora is in fact using the updated method.
Most likely you will need "Required, Alternate Port" in order for that to work. Try it out, see if email still transfers, and verify that you're seeing TLSv1.2 per above.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Zo K,
You are correct sir. After selecting "Required Alternate Port", under "Checking Mail", the "Last SSL Info" showed TLSv1.2. It works! So that's what that button is for!
Strangely enough though, selecting any of the three TLS options under "Sending Mail" yields the same result: "You have never sent mail using an SSL connection with this personality since the last time you started Eudora (or a negotiation is in progress with the personality)". Since I have only one personality and all of the test emails were both sent and received with the same TLS option checked, I'm not sure why none of the options yields a TLSv1.2 on the send side. Hopefully not important.
Computers 11,396 Alan Barr 3.5 : )
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Maybe you're using a "relay" personality for the sending part. Remember, for both sending and receiving, you have to check each personality, plus the main setting under Tools/Options (Checking Mail and Sending Mail).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Zo K:
Well, the "Use relay personality if defined" is checked for the only (<dominant>) personality. The SSL settings are the same on the Personality Properties as those I set in the Tools options where "Use submission port (587)" is checked, and SMTP Relay Personality is set to <dominant>. Could it be that the receiving SMTP server is not yet supporting TLS, so TLS isn't used?</dominant></dominant>
I really appreciate your taking this kind of time to help out me out. Hopefully this will be useful to a lot of other people reading the discussion board. I think it might be wise to wait until August 9th when ionos switches over their system to see if I have problems before badgering y'all with more questions. Thanks again for the help.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
There is some personality, either the dominant one or a different one, through which you are sending mail. That one should display Last SSL info, assuming you've sent email since last time you started Eudora.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I thought I owed y'all an update on your fine work. I loaded the four new files from Pete into Eudora and selected "None" under SMTP Relay Personality for sending mail as per Zo K's suggestion, and voila! - a working Eudora on both the office and home Windows 7 computers, complete with TLSv1.2 indicated on the Last SSL Info. Thanks a million!
That encouraged me to try the same thig on the Windows 10 computer at the office, which showed error reports with the cetificates at first on both send and receive. After some other sleuthing, I went into Personalities, found the skull and cross bones, and ended up trusting that server certificate, which cured all the error messages and allowed me to send and receive mail. The Last SSL Info, though, says it is still TLSv1. Hmm. I did see Pete's other thread titled "TLS v1.2 for SMTP" describing this problem and indicating there is a way to force the use of TLSv1.2. Is that fix somewhere on this discussion board?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Telling Eudora to trust certificates it doesn't trust is bypassing part of the security of SSL, and you shouldn't be doing that. It sounds like something isn't working right on your Windows 10 computer.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If it makes you feel any better, the 'unknown error' message was produced even though it stated "Certificate bad: Destination Host name does not match host name in certificate But ignoring this error because Certificate is trusted". The certificated I added as trusted is "US, Pennsylvania, Chesterbrook, IONOS Inc., smtp.ionos.com" - my ISP server.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Just for everyone's information, today my ISP switched over to requiring TLS 1.2. I found that, using Pete Maclean's substitute files, both Eudora programs on Windows 7 computers worked like champs and showed "TLSv1.2" under "Last SSL info". The Windows 10 machine still showed "TLSv1" under "Last SSL info", but downloaded and sent email just fine nevertheless. I.e., Pete's work saved me many headaches and for that I am most grateful!! Even works on Windows 10!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ionos is working fine with Eudora on my Win7 and Win10 machines. I created an obstacle for myself by first installing Pete's solution on my business PC. It already had a newer version of vcredist.exe so Pete's version was blocked. What I didn't know was that the newer version enabled the three new dll files to work. I happily copied the new dll files to my wife's PC a few days later and suddenly Eudora would hang and throw the useless error message "Error Reading from Network. Cause: Connection closed by foreign host". Today, I tried without success to register the dll files and then searched for vcredist.exe on my wife's PC - nada. So I copied Pete's file into place, ran it and Eudora is again working as it should.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Pete Maclean's most recent update download contains only the three .dll files but not the rootcerts.p9b file that is referenced in his Release Notes. It appeared that the Hermes Mail download does not contain that file as well. Is it no longer necessary to install that 'certificates file' into the Eudora folder?
And thanks in advance for saving my bacon and 25 years of my email history if this Eudora update works and allows me to continue to use my old trusty program despite my ISP's new encryption requirements.
Sorry about that! I have now added rootcerts.p7b to the download. Installing this file was never an actual requirement, just a good thing to have.
Thank you so much, Pete! One last question before load the new files, if you will indulge me: your Release Notes refer to installing "rootcerts.p9b" while the file in the download is "rootcerts.p7b". My existing certificates file is "rootcerts.p7b" also.
Would I be wise to replace the three .dll's and then just replace the certificates file if I have issues? Or is there a "rootcerts.p9b" floating around there somewhere that I should use?
My bad! Sorry. The release notes should have said "rootcerts.p7b". I have now fixed that and left a new zip to download. I suggest replacing this certificates file regardless.
fwiw, here is a link to Pete's file repository
https://www.maclean.com/downloads/
and the direct link to his updates of qcssl
https://www.maclean.com/downloads/QCSSL_Update.zip
thanks Pete!!!
Okay folks. You may not believe this, but the four files have been replced and everything appears to be working perfectly! Of course ionos.com hasn't started restricting their acceptable forms of encryption yet, but I assume this tls 1.2 will meet their requirements. I consider this one of only a handful of victories in my lifetime war against computers. Thanks very much!
Incidentally, do I need to select "If Available, STARTTLS", "Required STARTTLS", or "Required, Alternate Port" under the "Secure Sockets when Sending/Receiving" options or is the appropriate setting automatically a feature of the new files? FYI, this was done on my Windows 7 system and I intend to next move on to my computer which is running Eudora perfectly on Windows 10.
You can check in Eudora to see what the "Last SSL Info" was for the given personality and look at the "SSL Version". You should see TLSv1.2 if Eudora is in fact using the updated method.
Most likely you will need "Required, Alternate Port" in order for that to work. Try it out, see if email still transfers, and verify that you're seeing TLSv1.2 per above.
Zo K,
You are correct sir. After selecting "Required Alternate Port", under "Checking Mail", the "Last SSL Info" showed TLSv1.2. It works! So that's what that button is for!
Strangely enough though, selecting any of the three TLS options under "Sending Mail" yields the same result: "You have never sent mail using an SSL connection with this personality since the last time you started Eudora (or a negotiation is in progress with the personality)". Since I have only one personality and all of the test emails were both sent and received with the same TLS option checked, I'm not sure why none of the options yields a TLSv1.2 on the send side. Hopefully not important.
Computers 11,396 Alan Barr 3.5 : )
Maybe you're using a "relay" personality for the sending part. Remember, for both sending and receiving, you have to check each personality, plus the main setting under Tools/Options (Checking Mail and Sending Mail).
Zo K:
Well, the "Use relay personality if defined" is checked for the only (<dominant>) personality. The SSL settings are the same on the Personality Properties as those I set in the Tools options where "Use submission port (587)" is checked, and SMTP Relay Personality is set to <dominant>. Could it be that the receiving SMTP server is not yet supporting TLS, so TLS isn't used?</dominant></dominant>
I really appreciate your taking this kind of time to help out me out. Hopefully this will be useful to a lot of other people reading the discussion board. I think it might be wise to wait until August 9th when ionos switches over their system to see if I have problems before badgering y'all with more questions. Thanks again for the help.
There is some personality, either the dominant one or a different one, through which you are sending mail. That one should display Last SSL info, assuming you've sent email since last time you started Eudora.
Zo K and Pete,
I thought I owed y'all an update on your fine work. I loaded the four new files from Pete into Eudora and selected "None" under SMTP Relay Personality for sending mail as per Zo K's suggestion, and voila! - a working Eudora on both the office and home Windows 7 computers, complete with TLSv1.2 indicated on the Last SSL Info. Thanks a million!
That encouraged me to try the same thig on the Windows 10 computer at the office, which showed error reports with the cetificates at first on both send and receive. After some other sleuthing, I went into Personalities, found the skull and cross bones, and ended up trusting that server certificate, which cured all the error messages and allowed me to send and receive mail. The Last SSL Info, though, says it is still TLSv1. Hmm. I did see Pete's other thread titled "TLS v1.2 for SMTP" describing this problem and indicating there is a way to force the use of TLSv1.2. Is that fix somewhere on this discussion board?
Telling Eudora to trust certificates it doesn't trust is bypassing part of the security of SSL, and you shouldn't be doing that. It sounds like something isn't working right on your Windows 10 computer.
If it makes you feel any better, the 'unknown error' message was produced even though it stated "Certificate bad: Destination Host name does not match host name in certificate But ignoring this error because Certificate is trusted". The certificated I added as trusted is "US, Pennsylvania, Chesterbrook, IONOS Inc., smtp.ionos.com" - my ISP server.
Just for everyone's information, today my ISP switched over to requiring TLS 1.2. I found that, using Pete Maclean's substitute files, both Eudora programs on Windows 7 computers worked like champs and showed "TLSv1.2" under "Last SSL info". The Windows 10 machine still showed "TLSv1" under "Last SSL info", but downloaded and sent email just fine nevertheless. I.e., Pete's work saved me many headaches and for that I am most grateful!! Even works on Windows 10!
Pete is our champion! eagerly awaiting the OAuth2
as ALWAYS - all hail Pete Maclean!
Ionos is working fine with Eudora on my Win7 and Win10 machines. I created an obstacle for myself by first installing Pete's solution on my business PC. It already had a newer version of vcredist.exe so Pete's version was blocked. What I didn't know was that the newer version enabled the three new dll files to work. I happily copied the new dll files to my wife's PC a few days later and suddenly Eudora would hang and throw the useless error message "Error Reading from Network. Cause: Connection closed by foreign host". Today, I tried without success to register the dll files and then searched for vcredist.exe on my wife's PC - nada. So I copied Pete's file into place, ran it and Eudora is again working as it should.