> On Nov 13, 2017, at 12:35 AM, Simon Matthews
> wrote:
>
> I installed letsencrypt and generated a certificate.
>
> Even with this certificate, I got the same error. The error went away
> when I changed the connection to "TLS" from "TLS (Accept All
> Certificates)".
>
> I wonder if the roo
I installed letsencrypt and generated a certificate.
Even with this certificate, I got the same error. The error went away
when I changed the connection to "TLS" from "TLS (Accept All
Certificates)".
I wonder if the root problem was that the mail app on my phone won't
accept newer certificates u
Use a publicly-trusted certification authority, such as Let's Encrypt.
The problem is from the remote side (it's sending the alert that it
does not recognize your certificate issuer).
-Kyle H
On Sun, Nov 12, 2017 at 7:47 AM, Simon Matthews
wrote:
> On Sun, Nov 12, 2017 at 4:55 AM, Jan Just Keijs
On Sun, Nov 12, 2017 at 4:55 AM, Jan Just Keijser wrote:
> Hi,
>
> On 12/11/17 05:39, Simon Matthews wrote:
>>
>> I have generated a new certificate for my CentOS 6/postfix server, and
>> it seems to work with most clients, but when I try to send email using
>> tls from my Android device, it alway
Hi,
On 12/11/17 05:39, Simon Matthews wrote:
I have generated a new certificate for my CentOS 6/postfix server, and
it seems to work with most clients, but when I try to send email using
tls from my Android device, it always fails.
In my postfix log, I see:
warning: TLS library problem: 13671:
I have generated a new certificate for my CentOS 6/postfix server, and
it seems to work with most clients, but when I try to send email using
tls from my Android device, it always fails.
In my postfix log, I see:
warning: TLS library problem: 13671:error:14094416:SSL
routines:SSL3_READ_BYTES:sslv
