I had sent you an email thanking you for the newest QCSSL, but found this forum and also want to publicly thank you and see if a description of my problem and how your patch fixed it might be helpful
I will do this soon as i am dead tired tonight, but wanted to at least say THANK YOU!!!!!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
So, this is my circumstance, in case it can be helpful to anyone
I had been successfully using Eudora with Godaddy's free Workspace email for 14+ years. Last month I was informed that Godaddy would be transitioning every email account onto the (fee-based) Microsoft 365, and was told that 365 would not work with Eudora, particularly after Oct 2022.
So i began the search for an email hosting company that would work with third party pop3/smtp clients, allowed catch-all accounts, and was reasonably priced
I checked around with 10+ different hosting companies, and whittled it down to 3:
Zoho, A2 and Siteground.
I tried all 3, and even though all 3 could receive my pop3 emails, all 3 failed to allow Eudora to smtp send (trying every possible combination of smtp ports and ssl settings) - none worked.
fwiw, Godaddy smtp continued to work with just the first QCSSL update, so presume they were still on an older version of TLS, and are not planning to update since they are phasing out their in house email hosting
The error messages were not detailed, simply: lost server connection and 530 5.1.1 authentication required (leading tech support to presume i had an incorrect password)
Spending dozens of hours working with each host company's tech support, there was only one potential solution found - A2 allows the sending of smtp email without tls/ssl (Eudora's "never" switch) - but that was not an optimum solution, particularly since Eudora does not encrypt the password (using only easily decoded base64 encoding).
I tried to find a way to manually update the smtp ssl certificate (as is done with pop3 last ssl certificate manager), but could never open that button, as it always says (even now while ssl smtp is working): "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 is personality)"
Then trying to import my 20+ year Eudora email database into Thunderbird (trying both the importer addon to a current version and also tried v17 of Thunderbird which was supposed to be the last version that importing worked well with), but it completely failed - I really didn't want to use it anyway ;)
I did successfully try pandora mail, and though i really appreciate the effort (which is still in active (2022) development/support) , imo, the UI still has a ways to go vs Eudora - even as it has some useful updated functionality
but LUCKILY, i found this site and the link to Pete's recent QCSSL update - thank you Pete!!!
So, it didn't seem to have anything to do with an updated SSL certificate (smtp or pop3) -for my use, Eudora simply needed the recently (Jan 2022) updated QCSSL package (with a current TLS implementation to allow the smtp authentication server handshake to complete)
And Pete tells me that he is confident that they will also be able to update Eudora to OAuth2 before the Oct 2022 hard date change at Microsoft Office 365 (and perhaps with other email hosters)
So again, thank you Pete!! You are our champion!!!
Last edit: crape mael 2022-05-04
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Good morning,
I am a 30+year happy Eudora user who seeks help. I have started using Eudora in the early ‘90s and have fought all the way through be able to use it in my IBM-centric corporate environment. I have a lifetime of emails stored in Eudora and I use it as a sort of archive, also thanks to its efficient search function. This just to explain why I am very reluctant to drop it.
Here is my situation: in the last 10 years more or less I have been running Eudora on win7 with the feb19 Hermes patch without any problem. I seem to remember that I had also installed the patch to shorten the timeout when connecting to the server. The Eudora setup I have is “authentication allowed”, “use relay personality” and “use submission port (587)”, “if available use STARTTLS” for incoming and “required STARTTLS” for outgoing mail.
My service provider requires the following:
SMTP: port 25 or 587 with STARTTLS-SSL/TLS (on iphone 587 with SSL & pw authentication)
POP: port 110 with STARTTLS-SSL/TLS (on iphone 993 with SSL & pw authentication)
IMAP: port 143
A month ago I switched to a new laptop running win11, installed Eudora 7.1.0.9, copied over the whole directory from the old laptop and everything worked like a charm.
A couple of days ago, without touching anything, Eudora started giving a failed SSL error message when popping mail. I have checked the last SSL report and found that it had attempted TLSv1 on port 110.
I have forced ports 995/587 in Eudora.ini but the error message changed to “connection to the server timed out”.
I have done several tests replacing the Hermes files with a July19 version and also with the office365 version that was provided here, just in order to get the log (which indeed shows that Eudora tries to use TLSv1).
I have also tried the old win7 laptop and have seen that it does not work there either.
Sending mail does work.
I have set up the account on MS office classic (POP port 995-SSL/TLS; SMTP port 587-STARTTLS) to exclude a server issue and indeed it works. POP also works on my iphone.
In the win11 internet options in the new laptop I have TLSv1.2 and 1.3 selected, have tried to select TLSv1.0 and 1.1 as well but it does not work.
I am not sure where to go from here, can you suggest options to troubleshoot (and hopefully solve) the issue ?
Thank you in advance.
Kind regards,
Alberto
Last edit: Alberto Gianolio 2026-02-25
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Pete, I sent you a direct email. Thanks!
Okay. I will digest this over the weekend.
Hi Pete
I had sent you an email thanking you for the newest QCSSL, but found this forum and also want to publicly thank you and see if a description of my problem and how your patch fixed it might be helpful
I will do this soon as i am dead tired tonight, but wanted to at least say THANK YOU!!!!!
Hi
So, this is my circumstance, in case it can be helpful to anyone
I had been successfully using Eudora with Godaddy's free Workspace email for 14+ years. Last month I was informed that Godaddy would be transitioning every email account onto the (fee-based) Microsoft 365, and was told that 365 would not work with Eudora, particularly after Oct 2022.
So i began the search for an email hosting company that would work with third party pop3/smtp clients, allowed catch-all accounts, and was reasonably priced
I checked around with 10+ different hosting companies, and whittled it down to 3:
Zoho, A2 and Siteground.
I tried all 3, and even though all 3 could receive my pop3 emails, all 3 failed to allow Eudora to smtp send (trying every possible combination of smtp ports and ssl settings) - none worked.
fwiw, Godaddy smtp continued to work with just the first QCSSL update, so presume they were still on an older version of TLS, and are not planning to update since they are phasing out their in house email hosting
The error messages were not detailed, simply: lost server connection and 530 5.1.1 authentication required (leading tech support to presume i had an incorrect password)
Spending dozens of hours working with each host company's tech support, there was only one potential solution found - A2 allows the sending of smtp email without tls/ssl (Eudora's "never" switch) - but that was not an optimum solution, particularly since Eudora does not encrypt the password (using only easily decoded base64 encoding).
I tried to find a way to manually update the smtp ssl certificate (as is done with pop3 last ssl certificate manager), but could never open that button, as it always says (even now while ssl smtp is working): "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 is personality)"
Then trying to import my 20+ year Eudora email database into Thunderbird (trying both the importer addon to a current version and also tried v17 of Thunderbird which was supposed to be the last version that importing worked well with), but it completely failed - I really didn't want to use it anyway ;)
I did successfully try pandora mail, and though i really appreciate the effort (which is still in active (2022) development/support) , imo, the UI still has a ways to go vs Eudora - even as it has some useful updated functionality
https://www.drivehq.com/web/brana/pandora.htm
https://pandoramail.com/
https://pandoramail.blogspot.com/2021/04/im-migrating-from-eudora-mail-client-to.html
but LUCKILY, i found this site and the link to Pete's recent QCSSL update - thank you Pete!!!
So, it didn't seem to have anything to do with an updated SSL certificate (smtp or pop3) -for my use, Eudora simply needed the recently (Jan 2022) updated QCSSL package (with a current TLS implementation to allow the smtp authentication server handshake to complete)
And Pete tells me that he is confident that they will also be able to update Eudora to OAuth2 before the Oct 2022 hard date change at Microsoft Office 365 (and perhaps with other email hosters)
So again, thank you Pete!! You are our champion!!!
Last edit: crape mael 2022-05-04
Thanks for this. The cantab.net domain switched to TLS1.2 only and this allowed me to keep using Eudora 7.1.0.9
Good morning,
I am a 30+year happy Eudora user who seeks help. I have started using Eudora in the early ‘90s and have fought all the way through be able to use it in my IBM-centric corporate environment. I have a lifetime of emails stored in Eudora and I use it as a sort of archive, also thanks to its efficient search function. This just to explain why I am very reluctant to drop it.
Here is my situation: in the last 10 years more or less I have been running Eudora on win7 with the feb19 Hermes patch without any problem. I seem to remember that I had also installed the patch to shorten the timeout when connecting to the server. The Eudora setup I have is “authentication allowed”, “use relay personality” and “use submission port (587)”, “if available use STARTTLS” for incoming and “required STARTTLS” for outgoing mail.
My service provider requires the following:
SMTP: port 25 or 587 with STARTTLS-SSL/TLS (on iphone 587 with SSL & pw authentication)
POP: port 110 with STARTTLS-SSL/TLS (on iphone 993 with SSL & pw authentication)
IMAP: port 143
A month ago I switched to a new laptop running win11, installed Eudora 7.1.0.9, copied over the whole directory from the old laptop and everything worked like a charm.
A couple of days ago, without touching anything, Eudora started giving a failed SSL error message when popping mail. I have checked the last SSL report and found that it had attempted TLSv1 on port 110.
I have forced ports 995/587 in Eudora.ini but the error message changed to “connection to the server timed out”.
I have done several tests replacing the Hermes files with a July19 version and also with the office365 version that was provided here, just in order to get the log (which indeed shows that Eudora tries to use TLSv1).
I have also tried the old win7 laptop and have seen that it does not work there either.
Sending mail does work.
I have set up the account on MS office classic (POP port 995-SSL/TLS; SMTP port 587-STARTTLS) to exclude a server issue and indeed it works. POP also works on my iphone.
In the win11 internet options in the new laptop I have TLSv1.2 and 1.3 selected, have tried to select TLSv1.0 and 1.1 as well but it does not work.
I am not sure where to go from here, can you suggest options to troubleshoot (and hopefully solve) the issue ?
Thank you in advance.
Kind regards,
Alberto
Last edit: Alberto Gianolio 2026-02-25