 |
 |
Matt, OK, but what exactly is the "cert thing" problem? The message I get now is that "Destination Host name does not match host name in certificate". Isn't that a bad thing that *all* e-mail clients should reject?? Seems to me that Eudora is the only one doing the right thing, any client that silently accepts this misbehavior is welcoming attacks. Why should we allow this name mismatch? Why not just use properly formed certificates in the first place? What am I missing??? Thanks, -- dkm (*not* Diane Waldie!) At Thu 24 Sep 2015 10:51:08 AM EDT, "Stehouwer, Matt" wrote: > It will support pop3 but if I remember that it a cert thing. > > Matt Stehouwer > Technology Manager > Michigan State University > College of Natural Science Deans Office > 288 Farm Lane RM 154 > East Lansing, MI 48824 > 517 355-9003 | Email: [log in to unmask] > Linked-In: www.linkedin.com/in/mattstehouwer/ > > > -----Original Message----- > From: Diane Waldie [mailto:[log in to unmask]] > Sent: Thursday, September 24, 2015 10:47 AM > To: [log in to unmask] > Subject: Re: [MSUNAG] Eudora problem > > Matt, > > What exactly does "they don't support Eudora" mean? Eudora is just a > POP3 client, and should work with any ordinary POP3 server. Will they have > no POP3 server? Will they still support Outlook as a POP3 client? Will > they monkey with their POP3 server specifically to break Eudora and other > non-MS POP3 clients? > > Thanks, > -- dkm > > > At Thu 24 Sep 2015 07:52:34 AM EDT, "Stehouwer, Matt" wrote: >> This is just my thoughts but I would be thinking of getting off Eudora. > MSU >> is going to retire Legacy mail with Exchange or Office 365 and they don't >> support Eudora. >> >> Matt Stehouwer >> Technology Manager >> Michigan State University >> College of Natural Science Deans Office >> 288 Farm Lane RM 154 >> East Lansing, MI 48824 >> 517 355-9003 | Email: [log in to unmask] >> Linked-In: www.linkedin.com/in/mattstehouwer/ >> >> >> -----Original Message----- >> From: Chris Wolf [mailto:[log in to unmask]] >> Sent: Thursday, September 24, 2015 7:46 AM >> To: [log in to unmask] >> Subject: Re: [MSUNAG] Eudora problem >> >> This did work to fix the current MSU certificate problem, requiring three >> iterations to add each of the new untrusted certificates in sequence. >> >> -----Original Message----- >> From: Chris Wolf [mailto:[log in to unmask]] >> Sent: Thursday, September 24, 2015 7:33 AM >> To: [log in to unmask] >> Subject: Re: [MSUNAG] Eudora problem >> >> 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' >