 |
 |
Yay! It eventually worked for me too! In my case, I had to go 8 layers deep, with multiple restarts. The final cert from East Lansing goes through 3 different Certificate Authorities, including ones in Ann Arbor and New Jersey. Seems like generally suspicious behavior, Eudora is right to reject this nonsense, shame on all the other clients! This nonsense only took away 1 hour of my work day, with three calls to MSU Help Desk. Still waiting for details on why exactly the upcoming mail system will not work with an ordinary POP3 client like Eudora. I would gladly update to a newer, "supported" POP3 client, as long as it was not Outlook, Thunderbird, or Eudora OSE. Anybody have any ideas? Thanks, -- dkm (replying using Eudora, so my name should definitely show correctly now!) At 9/24/2015 11:30 AM Thursday, STeve Andre' wrote: >Thanks to Chris for this link. It has indeed fixed the problem. The key >to this is remembering the chain here, such that you have to go multiple >levels to fix the problem (trust the cert). > >I thank you all for the help. > >--STeve Andre' > >On 09/24/15 07:32, Chris Wolf wrote: >>This will probably fix the problem: >>http://blog.timeoff.org/rick/2015/09/09/revisiting-eudora-ssl-certificate-fa >>ilures/ >> >>I used this a month ago to fix the same type of certificate problem with >>Comcast servers, and I'll be trying it shortly with the current MSU problem. >> >> >>-----Original Message----- >>From: STeve Andre' [mailto:[log in to unmask]] >>Sent: Thursday, September 24, 2015 12:48 AM >>To: [log in to unmask] >>Subject: [MSUNAG] Eudora problem >> >>So, for my anniversary of starting at MSU, I get a present of Eudora not >>working, owing to a expired certificate. I don't think I have any Eudora >>users working at the moment. >> >>There is a tech base article tb158 which didn't work for me. >> >>Has anyone else crashed into this problem and how was it fixed? >>I can enter what I'm seeing tomorrow. Right now I'm about to fall down. >>;-) >> >>--STeve Andre'