Entourage Certificate Problem

[pmdegroot]

Version: 2008
Operating System: Mac OS X 10.5 (Leopard)
Processor: Intel
Email Client: imap

My Mac Mail accepts the certificate, but Entourage doesn't. All the settings are correct. Then we read that Entourage has a bug: namely that it does not accept certificates where the IP address and name are different. Is this really true???

 

[Corentin Cras-Méneur]

My Mac Mail accepts the certificate, but Entourage doesn't. All the
settings are correct. Then we read that Entourage has a bug: namely that
it does not accept certificates where the IP address and name are
different. Is this really true???

Not sure it's a bug.... It sounds like a problem in the certificate to
me (and Mail would be dismissing the issue).
You you have any kind of mismatch in the certificate??


Corentin

 

[pmdegroot]

I would imagine there is something in the certificate Entourage doesn't like. What that is I have no idea. What should I be looking for? What do you mean by a mismatch?
Thanks for your help

 

[William Smith [MVP]]

My Mac Mail accepts the certificate, but Entourage doesn't. All the
settings are correct. Then we read that Entourage has a bug: namely
that it does not accept certificates where the IP address and name
are different. Is this really true???

I don't think you've provided enough information to give you a good answer.

Whose certificate? What settings do you have?

--

bill

Entourage Help Page <http://entourage.mvps.org/>
Entourage Help Blog <http://blog.entourage.mvps.org/>
YouTalk <http://nine.pairlist.net/mailman/listinfo/youtalk>
Twitter: follow <http://twitter.com/meck>

 

[pmdegroot]

The certificate is mail.firstmedcenters.com
The IMAP server is 60.68.160.136
Receiving mail: Secure SSL, IMAP port 993
Outgoing mail: SMTP requires authentication (same settings), SMTP port 25

Please let me know what other info you need.

 

[Diane Ross]

SMTP port 25

You might try 2525 instead.

 

[pmdegroot]

The SMTP port change to 2525 has no effect. I cannot email, let alone send.

Thanks

 

[Mike VanHorn]

The certificate is mail.firstmedcenters.com

That sounds like the name of the server, not a certificate.

Outgoing mail: SMTP requires authentication (same settings), SMTP port 25

If your outgoing (SMTP) server really does require SSL,try changing the port
to 465. That's what we have to do where I work.

What does keychain access say about the certificate you are trying to use? I
know in my case Keychain Access says the certificate is "valid", but
Entourage still reports that it "did not find any valid certificates on the
Mac OS keychain".

 

[pmdegroot]

Still no luck even with 465.. Entourage does not like the certificate it seems. I could email a print screen of the certificate. The name is as I said.

I'm at a loss. How can I check how to solve the certificate issue.

Thanks

 

[Corentin Cras-Méneur]

Still no luck even with 465.. Entourage does not like the certificate it
seems. I could email a print screen of the certificate. The name is as I
said.

That won't help. Is the certificate properly listed in your keychain??
(check with the Keychain Access application)


Corentin

 

[pmdegroot]

The certificate is listed in the Keychain Access Application. What do you mean by properly listed? It is there.

 

[Corentin Cras-Méneur]

The certificate is listed in the Keychain Access Application. What do you
mean by properly listed? It is there.

In Tiger it has tobe in the X509Anchor
In Leopard, in the Login keychain.

I keep on thinking that there must be something wrong with the
certificate if Entourage still rejects it :-\


Corentin

 

[pmdegroot]

Well we are going round in circles..... obviously if Mac Mail accepts the certificate it can't be completely bad! The only question is what is wrong with the certificate or to put it in other words, what doesn't Entourage like about our certificate. Is there some test you can do to check it? Then at least we'd know what to do.

Thanks

 

[pmdegroot]

Well we are going round in circles..... obviously if Mac Mail accepts the certificate it can't be completely bad! The only question is what is wrong with the certificate or to put it in other words, what doesn't Entourage like about our certificate. Is there some test you can do to check it? Then at least we'd know what to do.

 

[Corentin Cras-Méneur]

Well we are going round in circles..... obviously if Mac Mail accepts
the certificate it can't be completely bad!

Well as I was saying, Mail can accept a certificate that has a minor
conflict and it s possible that Entourage is more picky about this.
In addition, did you ever get a dialog in Mail telling you about the
conflict and allowing you to override it?? This happens with Web
Browsers for secure sites and the override setting doesn't propagate to
other apps.
Entourage doesn't offer such option.

The only question is what is
wrong with the certificate or to put it in other words,

Well I don't know. I can't see or use your certificate so I can't tell.

what doesn't
Entourage like about our certificate. Is there some test you can do to
check it? Then at least we'd know what to do.

All you said was that Entourage doesn't accept it. I need far more than
that to have a decent opinion. WHat happens exactly?? Do you get an
error message?? Anything at all??

Corentin

 

[pmdegroot]

OK, now we are getting somewhere... thanks: Yes there is a message in Mail and it asks me whether I want to connect. I then just connect. In Entourage, the error cites that the Certificate name and IP name are different.......

The name is mail.firstmedcenters.com
The IP address is 62.68.160.136

Thanks

 

[Corentin Cras-Méneur]

OK, now we are getting somewhere... thanks: Yes there is a message in
Mail and it asks me whether I want to connect. I then just connect. In
Entourage, the error cites that the Certificate name and IP name are
different.......

That's what I meant: Mail allows you to overlook the problem (which, by
the way, is a potential security threat).

The name is mail.firstmedcenters.com
The IP address is 62.68.160.136

If you look up the domain name, it should be 217.20.138.82.
The certificate is not valid and whoever issued it needs to correct it.

Corentin