Lilla said: > The drawback is that all domains gives the same SSL-cert so people will > always get one warning when they enter your login-page
I have faced this several times. My preferred approach at this point is to set up a "secure" host on one "main" domain. So, if I'm running hutnick.com and hosting for buddy1.org and buddy2.net I might set up the SM installs as such: https://secure.hutnick.com/buddy1org/webmail/ https://secure.hutnick.com/buddy2net/webmail/ or maybe just: https://secure.hutnick.com/buddy1org/ https://secure.hutnick.com/buddy2net/ This might seem sub-optimal at first, but webmail users are likely to bookmark and forget an ugly URL, but every browser that I know of (rightly) won't let you accept a cert for a wrong host "forever." They /will/ let you accept a cert from an unknown authority forever. To summarize, teaching users to just hit accept for dubious certs: bad. Teaching them that Verisign and Thawte aren't the end-all-be-all: good. Ugly URL: bad, but the lesser of two evils. -Peter PS: Let me emphasize that I think you are using hostnames the smart way, and I admire your use of virtual hosting, but the practicalities of SSL are not conducive to doing things the "smart" way in this case. -P ------------------------------------------------------- This SF.net email is sponsored by: Get the new Palm Tungsten T handheld. Power & Color in a compact size! http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en -- squirrelmail-users mailing list List Address: [EMAIL PROTECTED] List Archives: http://sourceforge.net/mailarchive/forum.php?forum_id=2995 List Info: https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
