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:
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
Avast users report that its certificate manager has blocked the updated Verizon Certificate. Apparently you have to manually accept it. Hope it works for you.
Something similar may be true for other Network security suites
I don't have Avast. Thanks for your suggestion, but manual acceptance of cert. doesn't fix the problem. The problem is caused by Verizon's updating their SSL servers very early last Thursday morning.
Yes, Joe. I tried turning off AVG and reaccepting certificates manually - no joy.
Problem sending also occurred in 2013. Went back to find it under "Problems sending email":
I've just tried that fix again and it's working.
Find your Eudora.ini file and under "Setting" add:
SmtpAuthBanished=CRAM-MD5
I had the same issue last week.
SSL Negotiation Failed: Unknown Error
Certificate bad: Destination Host name does not match host name in certificate
But ignoring this error because Certificate is trusted
The 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 tab
4. 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 tab
4. 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.
RadDadTX,
Your instructions worked on the Incoming mail -- thanks. But when I click on Last SSL info on the Generic (SMTP) side it tells me "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 this personality)" and does not give me access to the certificate information manager. I am still unable to send.
I've followed all the steps here.
I added 'SmtpAuthBanished=CRAM-MD5' to eudora.ini after 'SmtpAuthAllowed=1'
I added 'SmtpAuthBanished=CRAM-MD5' to deudora.ini after 'Settings' at the top.
I went to 'Personalities' and highlighted the only SSL cert with a skull and crossbones in "incoming mail'. (I can't do it in the 'Generic Properties'.)
I still can't get Eudora (Ver 7.1.0.9) to send emails. Receiving is not a problem.
Verizon is no help because it is not Outlook or 2 or 3 other email programs.
Anyone else have other suggestions? It started giving me the SSL error on 8/27/2015.
HEY GUYS, OUR EUDORA IS BACK!!!!!
WE HAVE A FIX!!!!!!!!!!!!!!!!!!
THANKS & KUDOS to Danny Weiss of the amazing Eudorafaqs.com web site for thinking of the final step to make it work!
To recap, the situation is that since Verizon changed it's SMTP certificate, our beloved Eudora has been jamming on sending and receiving mail.
We learned that to get the incoming mail to work, we need to
(1) Try to check mail; get error message about SSL certificate
(2) Right-click on personality and select Properties
(3) Select 'Incoming Mail' tab
(4) Click on 'Last SSL Info' button
(5) Select Certificate Information Manager
(6) Click on each + in the chain of certificates listed under 'Server' until we find the skull-&-crossbones one
(7) Select it, and click on 'Add to Trusted'
(8) Close out carefully ("Done", "OK") & close Eudora
(9) Open Eudora and try again.
(10) If the error persists, repeat the sequence and find the next unTrusted certificate, get it Trusted, and so on.
We hear that to get the outgoing mail to work, we need merely to do the same thing, but use the "Generic Properties" tab instead of the "Incoming Mail" tab. BUT, for many of us, that simply hasn't worked. We select "Last SSL Info", but we just get an error message saying that we have never sent email using an SSL connection wtih this personality. Without access to the "Last SSL Info" > Certificate Information Manager, we can't get any further.
ENTER DANNY WEISS!!!
Danny suggested that on the "Properties" window (the window that pops up when we right-click the personality), on the "Generic Properties" tab, we should UNCHECK the box that says "Use relay personality, if defined."
So I unchecked the box. I closed the window. I repeated the steps.... IT WORKED!!! This time, when I clicked on "Last SSL info", I got a grey window similar to the one I had obtained on the "Incoming Mail" side. This time, I was able to select the Certificate Information Manager, find the skull-and-bones certificate, and "Add to Trusted".
Needless to say, the problem was Verizon's new certificate.
THAT'S IT!!!!
Please write and tell me that all of you are now sending and receiving again!
❤️ Elana
So far two messages successfully sent. Thanks to all who contributed to a solution. Eudora has abilities that I haven't been able to find in any other mail client and I would hate to have to switch.
Start a new topic or ask questions in the open forum.
