The fix is meant to be applied server-side, but not on mail2web or other hosted Exchange, as it’s rare they would let you install your own SSL certificate. Instead, you are installing the SSL certificate on the web server where your actual mail domain is pointed to (e.g. blah.com). The problem is that Entourage uses the mail address suffix to look for the autoconfig and other stuff on the domain pointed at by the suffix, so if your email address is joe@blah.com, then Entourage will try to contact blah.com over SSL, which then gives the certificate errors.

This is great. We are having this exact issue. I followed you right up to the fix, then lost you. Your situation gives the example of a hosted Exchange server, but I do not know how to apply this fix in a hosted scenario. Or, did I miss the point and you mean that the fix is supposed to be applied server side to web server itself (vis a vis domain.com instead of mail2web)?

I realize you wrote this in June, but hopefully you get this and will be able to help!

Thanks,
Bret