Hi Aki,

I don't purchase anything. It's installed in the server when install qmailtoaster. Please suggest the procedure.

On Fri, Sep 14, 2018 at 5:15 PM Aki Tuomi aki.tuomi@dovecot.fi wrote:

The certificate has wrong subject, the certificate has a local issuer which isn't probably installed to your machine's trust store. So you should probably make sure the cert has correct subject (server's DNS name) and that you install the issuer as trusted issuer, or get a cert from a trusted provider.

Aki

On 14.09.2018 11:27, ChandranManikandan wrote:

Hi Friends,

Am facing the serious issue in outlook 2016.

When i tried to configure the email in outlook 2016 it's asking encrypted connection and checked automatically and if not available then it showing unencrypted. but finally unable to configure the email account in outlook 2016 and not permitted.

Do i need to update any in the server.

Am using COS 6 32 and 64 bit servers with qmailtoaster + dovecot 2.2.7.

Currently configured in outlook 2010 it's working without any issue. And always showing in outlook 2010 when i open the account. Do you want to continue yes or no for the certification. Because i have configured in advanced selected Auto in outlook 2010. If i select none it was not working the email.

Anyone facing the same issue.

How do i rectify it in outlook 2016 and how can i stop the certificate warning message in outlook.

If possible to use without encryption and what's the configuration.

Please advice and let me know the process.

Am seriously cannot access the email from outlook. I have attached the message while open outlook. If i click yes then it will open

Is the certificate expired. How do renew it or reload it with the fresh certificate.

--

*Thanks & Best Regards, Manikandan.C *

--

*Thanks & Best Regards,Manikandan.C*

On Fri, 14 Sep 2018, ChandranManikandan wrote:

I don't purchase anything. It's installed in the server when install qmailtoaster.

That's the problem -- a stranger has no assurance that the certificate you're presenting actually belongs to your server or someone pretending to be you. Hence the mail reader warning.

Please suggest the procedure.

You got 3 options:

1) Create your own self-signed certificate and have your
users import it.  This may work with small installations
where trust is a phone call away.

2) Install a ACME Certbot to install a Let'sEncrypt
certificate that gets renewed every few months.

3) Purchase a certificate from a recognized CA (sich as
Verisign/Thawte/whoever) and install that.

If you got a few bucks to spend and lacking in technical expertise, 3 is your best option. Instructions?

http://lmgtfy.com/?q=Obtaining+a+CA+signed+certificate

Joseph Tam jtam.home@gmail.com