[NFBCS] Certificate cannot be verified.

[carcione at access.net]

Now I get an error when I send, but it sends anyway.

Yeah, I think my provider’s tech guy should have been able to figure this out, but he didn’t.  But I am not paying a lot.

Tracy

 

 

From: NFBCS <nfbcs-bounces at nfbnet.org> On Behalf Of Curtis Chong via NFBCS
Sent: Wednesday, May 3, 2023 1:39 PM
To: 'NFB in Computer Science Mailing List' <nfbcs at nfbnet.org>
Cc: Curtis Chong <chong.curtis at gmail.com>; carcione at access.net
Subject: Re: [NFBCS] Certificate cannot be verified.

 

Hello Tracy:

 

I am glad this was so easy to resolve. This is something that your email service provider should have been able to help you with. I surely hope you aren't paying those folks tons of money.☺

 

Cordially,

 

Curtis Chong

 

-----Original Message-----
From: NFBCS <nfbcs-bounces at nfbnet.org <mailto:nfbcs-bounces at nfbnet.org> > On Behalf Of Tracy Carcione via NFBCS
Sent: Wednesday, May 03, 2023 11:34 AM
To: 'NFB in Computer Science Mailing List' <nfbcs at nfbnet.org <mailto:nfbcs at nfbnet.org> >
Cc: carcione at access.net <mailto:carcione at access.net> 
Subject: Re: [NFBCS] Certificate cannot be verified.

 

I got hold of Microsoft Disability.  It took their tech some time, but she

solved my problem.  She changed my email server setting from SSL to non-SSL.

 

And, as I suspected, fixing the certificate error also fixed the problem of

Jaws not reading message titles, so it really was a kind of disability

problem and not just an Outlook problem.

Thanks all for your advice.

Tracy

 

 

-----Original Message-----

From: NFBCS <nfbcs-bounces at nfbnet.org <mailto:nfbcs-bounces at nfbnet.org> > On Behalf Of Brian Buhrow via NFBCS

Sent: Tuesday, May 2, 2023 5:31 PM

To: NFB in Computer Science Mailing List <nfbcs at nfbnet.org <mailto:nfbcs at nfbnet.org> >

Cc: Brian Buhrow <buhrow at nfbcal.org <mailto:buhrow at nfbcal.org> >; carcione at access.net <mailto:carcione at access.net> 

Subject: Re: [NFBCS] Certificate cannot be verified.

 

          hello Tracy.  I suspect the problem is not with the certificate

itself, but rather that there is a missing certificate between the one it's

presenting to you and the root certificate it's using.  If you don't feel

comfortable sending the certificate info to the list, feel free to send it

to me privately and I'll see if I can track down the missing certificate for

you to install.  If possible, send me the certificate itself, but if you

cannot do that, send the detailed page showing all of the certificate data.

-thanks

-Brian

 

 

_______________________________________________

NFBCS mailing list

NFBCS at nfbnet.org <mailto:NFBCS at nfbnet.org> 

http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org

To unsubscribe, change your list options or get your account info for NFBCS:

http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/carcione%40access.net

 

 

_______________________________________________

NFBCS mailing list

NFBCS at nfbnet.org <mailto:NFBCS at nfbnet.org> 

http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org

To unsubscribe, change your list options or get your account info for NFBCS:

http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/chong.curtis%40gmail.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/nfbcs_nfbnet.org/attachments/20230503/948f4bd9/attachment.html>