Same problem here. Have had previous time sinks and learned Verizon doesn't seem to know much
about interfacing with Eudora. Awaiting a fix from folks here.
This problem is widespread among Eudora users. My problem also began on early Thursday morning, Matt. The SSL certificate being rejected is owned by Verizon, according to Wikipedia.
I spent at least an hour yesterday afternoon with Daniel, a Verizon tech support guy out of CA. He remotely accessed my system to get familiar with Eudora 7.1. Although Verizon doesn't support Eudora, he is going to download the client, work with it, and contact me at 11:30 AM EST on Monday. I hope he has good news then.
I reported this problem in another thread on Thursday morning, the 27th. Search my userID, Joe63, for details.
Joe
I had the same issue last week.
SSL Negotiation Failed: Unknown ErrorCertificate bad: Destination Host name does not match host name in certificateBut ignoring this error because Certificate is trustedThe connection with the server has been lost.Cause: (200)1. You need add the new SSL certificate to the trusted list. In Eudora, Click Tools > Personalities on the menu.2. In the personalities window, right-click on the personality and select Properties.3. Click on the Incoming Mail tab4. Click on the Last SSL info button.5. Click on the Certificate Information Manager button.6. In the Server Certificates area click on the + until you expand/get to the bottom.The certificate in question may have a skull and cross bones icon. Click that certificate to highlight.7. Click the Add to Trusted button and OK to close out the screen.8. I had to do this two times to accept two certificate updates.
I did this with my computer and wifes computrer off and on for the past several days. Sometimes it works for one or two tries, then fails again with a "SSL negotiation failed" error. Clicking yes within the message box does nothing.
I have to think Verizon IT is updating their server code and killing Eudora. This sort of thing has been going on for more than a year, time after time, after time, with fixes coming from their customers, not Verizon.
They tell me to use their email directly. Well, it's obvious the persons advising this have never used their tiny, primitve text editor screen while being bombarded with ads and scripts.
A recent Comcast offering is looking better and better.
@ameridaddy wrote: I did this with my computer and wifes computrer off and on for the past several days. Sometimes it works for one or two tries, then fails again with a "SSL negotiation failed" error. Clicking yes within the message box does nothing.I have to think Verizon IT is updating their server code and killing Eudora. This sort of thing has been going on for more than a year, time after time, after time, with fixes coming from their customers, not Verizon.They tell me to use their email directly. Well, it's obvious the persons advising this have never used their tiny, primitve text editor screen while being bombarded with ads and scripts.A recent Comcast offering is looking better and better.
Email providers have to make changes to keep up with the latest protocols. The issue is that normally, the email client providers are also updating their software to keep up. Eudora is not being updated anymore, and will continue to have issues like this. Users will keep finding workarounds for as long as possible, but it is not the ESP's responsibility to make sure their email is backwards-compatible with every defunct email client in existence.
There are several alternatives to the verizon.net/Eudora combo that don't require an ISP change or using webmail. The ones I would recommend most are:
1. Get an email address that is not ISP-dependent (such as Gmail).
2. Get an email client that is currently supported by the company that created it (Outlook, Thunderbird, etc.).
Curious as to what protocol was changed as the pop.verizon.net certificate updated OK (receive mail) and prevent the smtp.verizon.net certificate from updating (send mail)??? smtp.verizon.net expired on Aug 30, 2015.
Old Certs:
New Certs:
RadDadTX wrote:
"1. You need add the new SSL certificate to the trusted list. In Eudora, Click Tools > Personalities on the menu.2. In the personalities window, right-click on the personality and select Properties.3. Click on the Incoming Mail tab4. Click on the Last SSL info button.5. Click on the Certificate Information Manager button.6. In the Server Certificates area click on the + until you expand/get to the bottom.The certificate in question may have a skull and cross bones icon. Click that certificate to highlight.7. Click the Add to Trusted button and OK to close out the screen.8. I had to do this two times to accept two certificate updates."
This failed to help me as I noted above, but in trying it, I noticed I could not open "Certificate Information Manager" under the "General" tab.
Long story short, to access this, there first has to be a transaction failure to activate access to it. Solution:
1. Send yourself an email.
2. Upon receiving the failure notice, go back to RadDadTX's 1. above, but click on the "General" tab in the window instead of the "Incoming" tab and you will get the same options for the outgoing side of things.
I found the skull and crossbones on both sides, did the RadDadTX procedure on both the "General" and "Incoming" sides and now everything works.
Thanks RadDadTX!
Correct. There are two areas:
Generic Properties area is for sending (smtp.verison.net) and Incoming Mail for receiving (pop.verizon.net). Both have to be done separately.
I had several users trust the new inbound/outbound certificates with no issue. One user I had to Export all the certificates from another user and Import them manually to get outbound working.
mattchao wrote:... I get a "SSL certificate rejected," or something like that. .....
Matt -
This sounds like a problem with an expired certificate, I think the following link from the Eudora FAQs web site will be helpful. It describes a complete procedure for telling Eudora how to accept a new certificate; see:
Fixing Certificate Trust Errors in Eudora for Windows
-Danny.