...
Due to the limits of the available information, SSL virtual host require
separate IP addresses. That can be done with Courier, too.
However, the option that I'd recommend is that you use the name of your
own service in your client settings. If you're "foo.com Hosting", then
have your clients all use "mail.foo.com" for their server when sending
and receiving, and they won't get any errors or warnings related to SSL.
There's no reason to make the setup any more complicated than that.
I have considered that last option, however, I was sorta hoping to cheat
and use all of my domains, having them as seperate entities. I have some
very non-technical customers that want a domain name, and they want their
email to be the same; foo_...@bar.com. However, I may still do that,
only having ssl for one domain.
Currently in apache, we have several domains using ssl, but the cert just
has a bad cn, so the user must deal with a warning from the browser. Still
sounds like it is time to update some specs. Thanx for the good info, tho.
:)
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GAT d--(---)@ s+:- a23 C++@ UL+++>++++$ P+>+++$ !E----(nano) W++ N+ o? K?
!w O- M@ V- PS--(+) PE++ Y+(++) PGP++ t 5 X+ !R- tv- b++ Dl+ D+ G e->++
h----(++) r+++ y+++(+++++)
------END GEEK CODE BLOCK------
8 messages in net.sourceforge.lists.courier-usersRe: [courier-users] courier certificates
