Root certificate exchange entourage problem

[Guy]

Hi,
While openning entourage I get the error - unable to establish a
secure connection to XXX.XXX.XXX.XXX because a correct root
certificate is not installed.
I tried to install a valid certificate according to the instructions
of the entourgae help but I get an error saying that the certificate
already exist.
Any ideas??

Thanks in advance,

Guy.

 

[Andreas Beutel]

While openning entourage I get the error - unable to establish a
secure connection to XXX.XXX.XXX.XXX because a correct root
certificate is not installed.
I tried to install a valid certificate according to the instructions
of the entourgae help but I get an error saying that the certificate
already exist.
Any ideas??

Hi Guy,

I had the same question last month for doing secure SMTP / IMAP. I installed
all required root certs (self signed CA) like described on the help-page and
even applications like Apple Mail can use them without any problems - but
Entourage only shows this anoying error message. This issue seems not to be
solved in SP1.

Andreas

 

[Jim Cowan]

I'm having the same issue. Our IT department is looking into it, but I don't
feel very confident in the outcome. Any other suggestions would be
appreciated!

Jim

 

[Barry Wainwright]

Hi Guy,

I had the same question last month for doing secure SMTP / IMAP. I installed
all required root certs (self signed CA) like described on the help-page and
even applications like Apple Mail can use them without any problems - but
Entourage only shows this anoying error message. This issue seems not to be
solved in SP1.

Andreas

I am using certificates OK in entourage - follow the tutorial here:

<http://www.entourage.mvps.org/smime/index.html>

 

[Andreas Beutel]

I am using certificates OK in entourage - follow the tutorial here:
<http://www.entourage.mvps.org/smime/index.html>

Hi!

Thanks for the link. This is exactly what I did! Especially step 6. I can
even view the root cert of the certification authority in the Microsoft Cert
Manager application, and do an export and so on. But Entourage does not use
it. Of course it's a self signed CA, but I could import the root cert into
IE, into Mozilla, Firefox, Thunderbird, even Apple Mail can use it right
from the system keychain.

I think if one application like Apple Mail can use this cert from the
keychain and even Microsoft Cert Manager shows it correctly, it's not with
the cert, but how Entourage uses it.

I have no idea how to fix this - and I fear it's really an Entourage issue.
I use MS Entourage 11.1.0 on OS X 10.3.5.

Andreas

 

[Andreas Beutel]

Thanks for the link. This is exactly what I did! Especially step 6. I can
even view the root cert of the certification authority in the Microsoft Cert
Manager application, and do an export and so on. But Entourage does not use
it. Of course it's a self signed CA, but I could import the root cert into
IE, into Mozilla, Firefox, Thunderbird, even Apple Mail can use it right
from the system keychain.

I think if one application like Apple Mail can use this cert from the
keychain and even Microsoft Cert Manager shows it correctly, it's not with
the cert, but how Entourage uses it.

I have no idea how to fix this - and I fear it's really an Entourage issue.
I use MS Entourage 11.1.0 on OS X 10.3.5.

Hi,

I'm sorry, I finally could resolve the problem. It's half my fault, half the
fault of the German Entourage error message. The (German) error message
always refers to a wrong _root_ certificate. This is very confusing because
the reason for the error message is that the DNS-Name of the server and the
name in the certificate are not identical and therefore mismatch. Other
web/mail clients issue more precise messages about this, so one can figure
out it's not the _root_ certificate but the current certificate of the
server or in particular its name.

Again my apologies. Who does the translation of the error handling? Maybe
this could be adressed and improved in a future release?

Andreas

 

[Barry Wainwright]

Hi!

Thanks for the link. This is exactly what I did! Especially step 6. I can
even view the root cert of the certification authority in the Microsoft Cert
Manager application, and do an export and so on. But Entourage does not use
it. Of course it's a self signed CA, but I could import the root cert into
IE, into Mozilla, Firefox, Thunderbird, even Apple Mail can use it right
from the system keychain.

I think if one application like Apple Mail can use this cert from the
keychain and even Microsoft Cert Manager shows it correctly, it's not with
the cert, but how Entourage uses it.

I have no idea how to fix this - and I fear it's really an Entourage issue.
I use MS Entourage 11.1.0 on OS X 10.3.5.

Andreas

This is not as it should be. If it is available in the keychain I can see no
reason why Entourage cannot access it.

Checking my keychain, I find my Thawte certificates in all of the available
keychains; 'Login', MS_IntermediateCA_Certificates, MS_Entity_Certificates,
Microsoft_Intermediate_Certificates, Microsoft_Entity_Certificates.

Only the login keychain is unlocked.