U
useit
Does anyone know the reason why various versions of Outlook will throw the
following error:
"the server you are connecting to is using a security certificate that
could not be verified. A certification chain processed correctly, but
terminated in a root certificate that isn't trusted by the trust provider.
Do you want to continue to use this server?"
If you want to have a stab at it, take note:
The "self signed cert" has already been imported into the "trusted root
certification authorities" store. This can be verified when using the "
certificate management snap in" created with the MMC.
Further, the certificate is already currently working with various versions
of Thunderbird on Windows 2000/SP4, and works, also, with Apple Mail on OS
X 10.3 - 10.4.
For the more advanced; if anyone has a suggestion on how to make it work,
take note; here is some reference material from those who have gone before
you and disappeared without a trace...
Amongst all of the experts in these new groups, someone must surely know
the answer? Or, at least have some information as to why this problem
exists. Note, that free versions of software are able to perform this
"Enterprise" type service. READ: Secure encrypted authenticated SMTP.
Failing any solution, then begs the question; "What do corporate companies
do?" 1. Don't use Outlook, or surrender the functionality of secure mail?
Are there a million+ road warriors out there sending their email username &
passwords accross the Internet in "plain text"?
### Found ###
From: ********************************
Date: Wed, Sep 27 2006 10:04 am
Email: ++++++++++++++++++++++++++++++++
Groups: microsoft.public.outlook
[SNIP]
3) You need to make sure that the certificate is trusted by your
computer. To do that, make sure you have the appropriate CA certificate
in your local certificate store. Outlook 2007 is better in diagnosing
this issue, as it allows you to see the certificate in that dialog and
therefore better troubleshoot what the problem with the certificate it
(it could e.g. also be expired). If you can't fix the underlying
certificate issue, you'll just have to deal with this message.
QUOTE: "you'll just have to deal with this message"
--- ALSO ---
### Found ###
http://groups.google.com.au/group/m...ficate"+problem&rnum=2&hl=en#0dc7fb9adfb1b5c3
You will notice, that NO-ONE had any ideas.
following error:
"the server you are connecting to is using a security certificate that
could not be verified. A certification chain processed correctly, but
terminated in a root certificate that isn't trusted by the trust provider.
Do you want to continue to use this server?"
If you want to have a stab at it, take note:
The "self signed cert" has already been imported into the "trusted root
certification authorities" store. This can be verified when using the "
certificate management snap in" created with the MMC.
Further, the certificate is already currently working with various versions
of Thunderbird on Windows 2000/SP4, and works, also, with Apple Mail on OS
X 10.3 - 10.4.
For the more advanced; if anyone has a suggestion on how to make it work,
take note; here is some reference material from those who have gone before
you and disappeared without a trace...
Amongst all of the experts in these new groups, someone must surely know
the answer? Or, at least have some information as to why this problem
exists. Note, that free versions of software are able to perform this
"Enterprise" type service. READ: Secure encrypted authenticated SMTP.
Failing any solution, then begs the question; "What do corporate companies
do?" 1. Don't use Outlook, or surrender the functionality of secure mail?
Are there a million+ road warriors out there sending their email username &
passwords accross the Internet in "plain text"?
### Found ###
From: ********************************
Date: Wed, Sep 27 2006 10:04 am
Email: ++++++++++++++++++++++++++++++++
Groups: microsoft.public.outlook
[SNIP]
3) You need to make sure that the certificate is trusted by your
computer. To do that, make sure you have the appropriate CA certificate
in your local certificate store. Outlook 2007 is better in diagnosing
this issue, as it allows you to see the certificate in that dialog and
therefore better troubleshoot what the problem with the certificate it
(it could e.g. also be expired). If you can't fix the underlying
certificate issue, you'll just have to deal with this message.
QUOTE: "you'll just have to deal with this message"
--- ALSO ---
### Found ###
http://groups.google.com.au/group/m...ficate"+problem&rnum=2&hl=en#0dc7fb9adfb1b5c3
You will notice, that NO-ONE had any ideas.