as I know.
create your own root cert. use that root cert to sign your dovecot ssl cert. publish your public root cert in web server, and give instructions to your users to import this root cert once... then no more prompt on accepting the dovecot cert anymore.. this apply to www or other secure connection too.
Quentin
-----Original Message----- From: dovecot-bounces+quentin.chung=kts-group.com@dovecot.org [mailto:dovecot-bounces+quentin.chung=kts-group.com@dovecot.org] On Behalf Of Charles Marcus Sent: Wednesday, June 11, 2008 3:29 AM To: dovecot@dovecot.org Subject: Re: [Dovecot] outlook windows problem
On 6/10/2008 3:19 PM, rashantha de silva wrote:
hello, client can not connect using outlook.
has any of you noticed this problem. can not connect with imap or as pop. i am using a self signed certificate.
Not connecting to dovecot via SSL with a self-signed certificate? Try opening IE on that machine and going to https://yourmailserver:995 and accept the certificate permanantly. Then see if Outlook will connect.
thanks for the tip rick, but that would be strange request to make to a client.
Self-signed certs have always been a problem in OL (and I guess OE, but I don't use it or support it much)...
There is no way to permanently save one via the pop-up...
Meaning, the client will get the warning and have to accept it every tim they connect for the first time.
Nothing dovecot can do about that...
That said - it will work...
But again, would need more details... are your config details secret?
--
Best regards,
Charles