----- Original Message -----
From: "Vapor" <bluequartz (at mark) vaporised.com>
To: <coba-e (at mark) bluequartz.org>
Sent: Thursday, September 28, 2006 2:13 PM
Subject: [coba-e:07284] Re: Dovecot SSL warning (not error) [update2]
>> If you move a certificate from one server to another you may have
>> to get a new one re-issued.
>>
>> Certificate security is pretty tight to prevent fraud sights wrongly
>> being identified as kosher sites.
>
> I'm very familiar with Thawte SSL certs in a web context but not others
> and can say
> that Thawtes can be moved without issue as long as the domain used upon is
> as issued.
>
> I just didn't imagine that something as simple as encrypting email using
> SSL/TLS would
> be so problematic, certainly not needing yet more commericial
> certificates, what a
> shame. I will be transferring many SSL certs to this box when it's stable
> with all
> issues resolved hence my persistance.
>
> Well, it's technically doable at least with self signed certs so I'm half
> happy. Just
> need to work out how to get dovecot to use certs for the domain in
> question rather than
> just the one pointed to in the conf file. Maybe dovecot.conf allows
> environmental vars
> so certs could be referred to with local relative paths to a users/domains
> "home"?
>
> At least we have the functionality to play with with dovecot, thank you
> Hisao! :)
>
> Kindest
>
> Brett
Brett
I tested this on the server I have hosting my www.precisionweb.net site.
I set up the SSL for the server under the security section.
The server is named raq79.precisionweb.net
I used a $9.95 RapidSSL cert from www.enom.com so it is a real cert.
In my Outlook Express I set the incoming and outgoing mail servers to:
raq79.precisionweb.net
I no longer get the warnings.
So, I think the solution is to just get a real cert, then tell your
customers to connect to the server name instead of their individual domain
name.
----
Ken Marcus
Ecommerce Web Hosting by
Precision Web Hosting, Inc.
http://www.precisionweb.net