Re: Client app says my chained Comodo cert is invalid

2016-07-28 Thread Jerry Krinock
> On 2016 Jul 27, at 15:20, Joseph Tam wrote: > > Well, yes, that's what you would expect. You've told your mail client > to connect to "45.56.81.181", the client starts the SSL negotiation > and finds the certificate is made out for "sheepsystems.com", and your > mail client complains about th

Re: Client app says my chained Comodo cert is invalid

2016-07-27 Thread Jerry Krinock
> On 2016 Jul 27, at 15:20, Joseph Tam wrote: > > Well, yes, that's what you would expect. You've told your mail client > to connect to "45.56.81.181", the client starts the SSL negotiation > and finds the certificate is made out for "sheepsystems.com", and your > mail client complains about th

Re: Client app says my chained Comodo cert is invalid

2016-07-27 Thread Joseph Tam
The trouble appears when I attempt to configure a client account in Mail.app on my Mac. For the POP server name, I enter my VPS? ?45.56.81.181", because public DNS is still pointing to my existing host. I set the account to use the Apple TLS certificate, and then click to save this new account

Client app says my chained Comodo cert is invalid

2016-07-27 Thread Jerry Krinock
I’ve configured Dovecot and Postfix on a new VPS running Ubuntu 16.04, using Linode’s tutorial [1], to require authentication and SSL encryption for both POP3 and SMTP. All looks OK to me except, when my email client app (macOS Mail.app) tries to log in, it says that my cert is invalid. The t