On Wednesday, April 9, 2014 at 6:23:20 AM UTC+10,
er...@ericalbert.net wrote:
> Suddenly, my copy of Eudora 7.1.0.9, Paid Mode (running under Windows
> XP) is giving me an error message whenever I try to check my messages.
> (Details at end of this message.) I've been using Eudora with FastMail for
> years, and it was working fine yesterday. This problem is bringing my
> day to a standstill, so I'd appreciate how to fix this.
>
> I've tried clicking "yes" to accept the certificate for future sessions,
> and done some Googling for solutions (like going into the Properties
> window of my Eudora Personalities), but nothing has helped so far.
> Suggestions? Thanks!
>
> -- Eric
>
> Eudora's error message in the regular window at the bottom of the
> screen:
> = = = = =
> Fastmail, Logging into POP Server, [02:54:25 pm]
> SSL Negotiation Failed: Unknown Error The connection with the
> servers has been lost. Cause: (200)
> = = = = =
>
> Eudora's pop-up error window title:
> Server SSL Certificate Rejected
>
> Eudora's pop-up error window contents:
> = = = = =
> The server's SSL Certificate was rejected for the following reason:
>
> Unknown error
>
> Do you want to trust this certificate in future sessions?
> = = = = =
>
> The certificate itself, in the pop-up error window:
> Certificate:
> Data:
> Version: 3 (0x2)
> Serial Number:
> 01:fd:a3:eb:6e:ca:75:c8:88:43:8b:72:4b:cf:bc:91
> Signature Algorithm: sha256WithRSAEncryption
> Issuer: C=US, O=DigiCert Inc, OU=
www.digicert.com, CN=DigiCert
> Global Root CA
> Validity
> Not Before: Mar 8 12:00:00 2013 GMT
> Not After : Mar 8 12:00:00 2023 GMT
> Subject: C=US, O=DigiCert Inc, CN=DigiCert SHA2 Secure Server CA
> Subject Public Key Info:
> Public Key Algorithm: rsaEncryption
> RSA Public Key: (2048 bit)
> Modulus (2048 bit):
> 00:dc:ae:58:90:4d:c1:c4:30:15:90:35:5b:6e:3c:
> 82:15:f5:2c:5c:bd:e3:db:ff:71:43:fa:64:25:80:
> d4:ee:18:a2:4d:f0:66:d0:0a:73:6e:11:98:36:17:
> 64:af:37:9d:fd:fa:41:84:af:c7:af:8c:fe:1a:73:
> 4d:cf:33:97:90:a2:96:87:53:83:2b:b9:a6:75:48:
> 2d:1d:56:37:7b:da:31:32:1a:d7:ac:ab:06:f4:aa:
> 5d:4b:b7:47:46:dd:2a:93:c3:90:2e:79:80:80:ef:
> 13:04:6a:14:3b:b5:9b:92:be:c2:07:65:4e:fc:da:
> fc:ff:7a:ae:dc:5c:7e:55:31:0c:e8:39:07:a4:d7:
> be:2f:d3:0b:6a:d2:b1:df:5f:fe:57:74:53:3b:35:
> 80:dd:ae:8e:44:98:b3:9f:0e:d3:da:e0:d7:f4:6b:
> 29:ab:44:a7:4b:58:84:6d:92:4b:81:c3:da:73:8b:
> 12:97:48:90:04:45:75:1a:dd:37:31:97:92:e8:cd:
> 54:0d:3b:e4:c1:3f:39:5e:2e:b8:f3:5c:7e:10:8e:
> 86:41:00:8d:45:66:47:b0:a1:65:ce:a0:aa:29:09:
> 4e:f3:97:eb:e8:2e:ab:0f:72:a7:30:0e:fa:c7:f4:
> fd:14:77:c3:a4:5b:28:57:c2:b3:f9:82:fd:b7:45:
> 58:9b
> Exponent: 65537 (0x10001)
> X509v3 extensions:
> X509v3 Basic Constraints: critical
> CA:TRUE, pathlen:0
> X509v3 Key Usage: critical
> Digital Signature, Certificate Sign, CRL Sign
> Authority Information Access:
> OCSP - URI:
http://ocsp.digicert.com
>
> X509v3 CRL Distribution Points:
> URI:
http://crl3.digicert.com/DigiCertGlobalRootCA.crl
> URI:
http://crl4.digicert.com/DigiCertGlobalRootCA.crl
>
> X509v3 Certificate Policies:
> Policy: 2.5.29.32.0
> CPS:
https://www.digicert.com/CPS
>
> X509v3 Subject Key Identifier:
> 0F:80:61:1C:82:31:61:D5:2F:28:E7:8D:46:38:B4:2C:E1:C6:D9:E2
> X509v3 Authority Key Identifier:
> keyid:03:DE:50:35:56:D1:4C:BB:66:F0:A3:E2:1B:1B:C3:97:B2:3D:D1:55
>
> Signature Algorithm: sha256WithRSAEncryption
> 23:3e:df:4b:d2:31:42:a5:b6:7e:42:5c:1a:44:cc:69:d1:68:
> b4:5d:4b:e0:04:21:6c:4b:e2:6d:cc:b1:e0:97:8f:a6:53:09:
> cd:aa:2a:65:e5:39:4f:1e:83:a5:6e:5c:98:a2:24:26:e6:fb:
> a1:ed:93:c7:2e:02:c6:4d:4a:bf:b0:42:df:78:da:b3:a8:f9:
> 6d:ff:21:85:53:36:60:4c:76:ce:ec:38:dc:d6:51:80:f0:c5:
> d6:e5:d4:4d:27:64:ab:9b:c7:3e:71:fb:48:97:b8:33:6d:c9:
> 13:07:ee:96:a2:1b:18:15:f6:5c:4c:40:ed:b3:c2:ec:ff:71:
> c1:e3:47:ff:d4:b9:00:b4:37:42:da:20:c9:ea:6e:8a:ee:14:
> 06:ae:7d:a2:59:98:88:a8:1b:6f:2d:f4:f2:c9:14:5f:26:cf:
> 2c:8d:7e:ed:37:c0:a9:d5:39:b9:82:bf:19:0c:ea:34:af:00:
> 21:68:f8:ad:73:e2:c9:32:da:38:25:0b:55:d3:9a:1d:f0:68:
> 86:ed:2e:41:34:ef:7c:a5:50:1d:bf:3a:f9:d3:c1:08:0c:e6:
> ed:1e:8a:58:25:e4:b8:77:ad:2d:6e:f5:52:dd:b4:74:8f:ab:
> 49:2e:9d:3b:93:34:28:1f:78:ce:94:ea:c7:bd:d3:c9:6d:1c:
> de:5c:32:f3
> --- End Update ---
Thanks for your reply. I have read this entire thread and have tried a number of the suggestions given and I think that in doing so has caused me the latest problem I am experiencing.
When I first had the problem --- and it applies to all the personalities --- when I went into the Certificate Information Manager I could see all of the certificates. Then one of the posters suggested that he had gone to the certificate manager then clicked on "Add to Trusted" then hit OK a couple of times.
It was after doing this that when going to the Incoming Mail section in the Personalities and clicking on the "Last SSL" that I am getting the message that I quoted in my posting.
My basic process with Eudora when starting the program each day has always been that a dialogue box comes up individually for each of my five e-mail accounts, I enter the password (same one) for each of these and then the program goes and searches for and loads any new e-mail.
However since my problem started a couple of days ago, as soon as the program commences to search for the new e-mail I get the SSL Certificate error with a whole listing of computer talk (I have no idea what this all means, but I have seen a copy of a similar listing earlier in this whole conversation)for each of the personalities and at the bottom of the page appears a notice for each of the personalities that states --- 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) ---
If you can give any advice/assistance it will be greatly appreciated and I agree my hosting company (Netregistry) although the support person tried, he knew nothing about Eudora and basically said that I should contact them (now somewhat difficult !!!). All he could really tell me was that the company had forgotten to renew the certificate licence (or something) and that they had corrected this situation on the same day as I experienced the problem BUT he stated that "I should have experienced no interuption or problem when the certificate was renewed".
I will have a look for a couple of forums to see if I can find anything.
Again, thanks for your assistance.
David