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