I am one of those holdouts still using Eudora 18.104.22.168 as an e-mail client, in my case under Windows 7 Ultimate. Yes, I know it is an unsupported legacy application but, like many others, have used it a long time because I like a number of things about its functionality and especially don’t want to deal with switching to something else like Outlook unless and until Eudora no longer works at all. (I’ve also read that Eudora OSE and Thunderbird are not fully equivalent and also no longer supported either.)
Over the past few years, where Eudora was working just fine for a long period of time, I’ve had several problems sending mail which I’ve been able to fix, including an outgoing port number and a patch to the Eudora.ini file, both related to changes made by my current ISP (Verizon). However, I recently encountered a new issue involving an untrusted SMTP SSL certificate and, once again, I’ve found what appears to be a solution but this time I am less certain whether it is safe to proceed with the fix.
The error issued when sending mail says:
The server’s SSL certificate was rejected for the following reason:
Certficate Error: Unknown and unprovided root certificate.
Do you want to trust the certificate in future sessions?
This is followed by a display of the certificate and Yes / No buttons for accepting the certificate.
I have spoken with Verizon tech support and they tell me that no changes have been made to their SMTP server that should cause such a problem and that it is a client-side issue.
Through further digging, I found the Certificate Information Manager in Eudora through which this new certificate can be installed. So far, I have not actually gone ahead with this because of some concerns I have about whether this is totally safe to do.
For one thing, I note that the validity of the certificate is from 2000 through 2025, so clearly it has not expired. So, I’m wondering why the certificate would suddenly be rejected by Eudora.
One additional possible important detail is that I continue to maintain an email address with an old ISP (other than Verizon) I had in the past for a small monthly fee and receive mail directly through that ISP’s POP server. To send e-mail, I use the personality functionality of Eudora to generate messages using the domain name of my old ISP through the Verizon SMTP server. This had been working fine for a long time until this latest problem with the certificate. I’ve doubted whether this methodology has anything to do with this latest problem but include it here just in case.
What, other than the validity date, would cause a certificate to no longer be valid? Is there any risk in trusting this certificate as described above? Otherwise, is there a better way to fix this problem?
Thanks very much for the assistance.