"Seann" <[email protected]> wrote in message news:[email protected]... That is what I was figuring. Trying two different locations with the CA file I was using broke, when according to the list's information and my own reading it should work, turned out to require me to validate the CA file I was using again. What the case was, is I wasn't using OpenSSL to create the certs, as I have moved away from maintaining an OpenSSL CA to using the Microsoft CA, I grabbed a bundled cert, and it looks like it was split wrong. Downloading just the CA file itself fixed the issue and everything works perfectly now.
Now it is on to do the same thing with Dovecot, and then to make sure all the Authentication works correctly. Thanks for all your help! ~Seann I have used OpenSSL to generate the certificates when using Postfix with Active Directory. It is easy to separate the server certificate from the server key. How do you separate them when using Microsoft's certificate services? I can see the benefits of integrating Postfix with Windows PKI on a Windows network.
