Quote:
|
Originally Posted by IDtheTarget
Okay, I haven't had a chance to look into this yet, but that "trusted root authority" thing means that you're using a self-signed cert or a cert that comes from a "root authority" that's not in Blazer.
I'd like to know where you bought a $20 cert that is listed on the root authority table in Blazer! the cheapest I was able to find for our server at work was Entrust, which cost us $200.
If you use a self-signed certificate, rather than one that's been signed by a trusted root (such as Entrust or Verisign) and then installed on your server, you'll get that error.
I haven't had a chance to look at work-arounds in Versamail, and I probably won't until Monday. Sorry.  |
yep I know I was using a self signed cert. Hence my belief the problem was in VM not accepting it. and my point was that blazer let you override the untrusted cert whereas VM does not.
I bought an SSL cert from godaddy last night and installed it this morning.
I had to install the issued cert for my server and an intermediate cert that they also sent. I then reconfigured VM to use an SSL connection for activesync. As soon as I did that it worked fine! btw, the $20.00 is per year.
Blazer also no longer reports a problem with the cert when I go to that server's OWA page via https.
Is the entrust cert a one time fee?