Hi Blues,
Thats how its supposed to work I think.
If for example your clients domain is www.domain.com, and the
certificate is issued in that name, they will get no warning.
If however their mail server is say pop3.domain.com, and they
attempt to connect to pop3.domain.com top get their mail securely,
then a warning will be issued saying this certificate is not issued for
pop3.domain.com, but is www.domain.com.
Onother problem is each certificate I am pretty sure has to have a
unique IP.
Setting up secure certficates so you do not get warnings is not as
easy as it sounds. Especially with all the different types of OS.
Rgds.
Date sent: Sun, 1 Oct 2006 13:14:42 +0200
From: Maurice de Laat <muisnetw (at mark) xs4all.nl>
Send reply to: coba-e (at mark) bluequartz.org
Subject: [coba-e:07321] Re: Dovecot SSL warning (not error)
To: coba-e (at mark) bluequartz.org
[ Double-click this line for list subscription options ]
On Thu, Sep 28, 2006 at 03:39:00PM +0100, Connexions Web
Solutions
wrote:
> You will get this unless you use a properly chained certificate from
> a recognised authority.
Indeed. However, my users have another problem with the
certificate.
When they are connecting with POPS to their own virtual
domainname,
they receive a security warning that the certificate's domainname is
different from the domainname they are connecting to. The
certificate's domainname is the name from the box.
When the client uses the box's name as their POPS server, there
is no warning. Anyone know of a way to get rid of the warning while
still using the client's domainname as the POPS server?
Thank you
--
Maurice de Laat