 |
 |
And ATS followed through with the following link: http://www.eudora.com/techsupport/kb/2323hq.html . However, a) I don't know how any ordinary person who stumbles upon this error would find their way to this link (or should I have just Googled it myself?), and b) the linked page addresses the error "SSL Negotiation Failed: Certificate Error. Cert Chain not trusted. Try adding this certificate to your certificate database for SSL to succeed Certificate Error," instead of the error that I got, which was, "Certificate bad: Destination host name does not match host name in certificate," so I do not know yet if those instructions actually help in this case. -- dkm David McFarlane wrote: >Of course, I did not get Gary's message until after I got this error >myself and called it into ATS Help. The earnest young man there >claimed that this only affects Eudora users, but clearly he is >mistaken. He did, however, explain that this is indeed the result >of a misstep made during an update to the certificates last night, >and he is sending me instructions to fix this in Eudora. I asked >about putting a notice at help.msu.edu (which I dutifully checked >before calling ATS Help), he says that ATS plans to fix the >certificate problem shortly so it may not warrant a notice on the web site. > >-- dkm > > >>I'm sure people have already started to run into this today, but >>just to warn you, your users might be asking about >>this. Apparently they updated the mail.msu.edu ssl certificate >>this morning. The Service Status history suggests that "Many >>clients will not be affected", but so far that's not my >>experience. Outlook users doing sends here are getting prompted to >>accept a certificate that can't be verified. >>(Checking mail doesn't seem to prompt this, but sending mail >>definitely does seem to be.) >> >>(Personally, I'm seeing this on a Windows 7 machine running Office >>2007, all updates installed, and so far everyone that I know using >>outlook that I've asked has seen it. So I'd have to wonder about >>the "Many clients will not be affected."). >> >>One other note, I honestly don't remember seeing any sort of >>communication that this was happening, did I miss it? >> >>Gary