On Mon, 7 Jul 2003, Peter J. Holzer wrote:
On 2003-07-06 17:31:32 -0400, Sam Varshavchik wrote:
> Philipp Offermann writes:
> >I've a (quite expensive) signed web-server certificate. Is there any way > >to use this certificate also for smtp, pop3 and imap-connection for not > >getting any more warning?
> > You can, provided that:
> > * The certificate is not passphrase protected.
> > * The certificate is converted to a PEM format, in a single file that > contains both the private key, and the certificate.
* Your smtp, pop and imap servers are running on the same host as the webserver and the clients use the same name to access it (e.g., "www.mydomain.com", not "mail.mydomain.com". Otherwise the client will complain the names don't match.
Does anyone happen to know whether Courier works with wildcard certificates?
The server doesn't care what the certificate says. If you install a certificate, that's what will go out.
It's the client that needs to have support for wildcard certs.
That is, if bar.foo.com's cert's CN reads *.foo.com, the client has to accept it.
pgp00000.pgp
Description: PGP signature
