Resolved SSL Certificate Error for domain mail

[RobertoMa]

Hello,
i have Plesk 18.0.41 on my Virtual Server.
My server host Is: server.example.com
i have also added other domain with certificate wildcard and i added in domain mail setting the certificate. The SNI is active.
my problem is that when add mail [email protected] in client i have message certificate not safe.

the configuration DNS of domain.com is:

domain.com A ipserver
domain.com MX 10 mail.domain.com
mail.domain.com CNAME domain.com

i tried also put MX record to server.example.com but i have same error.
Please help me.

 

[Kaspar]

my problem is that when add mail [email protected] in client i have message certificate not safe.

What client?

 

[RobertoMa]

What client?

Spark Android

 

[Kaspar]

Do you can get a waring when you try to add the account to another client?

 

[RobertoMa]

Do you can get a waring when you try to add the account to another client?

No, i added in outlook 2019 desktop and eM Client desktop without problem.

 

[Bitpalast]

Spark-Android-App: Certs Issues - mailcow community

mailcow community - official community forum!

community.mailcow.email

 

[RobertoMa]

Spark-Android-App: Certs Issues - mailcow community

mailcow community - official community forum!

community.mailcow.email

Is it lets encrypt?

 

[Bitpalast]

The root certificate problem is Let's Encrypt related.

 

[RobertoMa]

The root certificate problem is Let's Encrypt related.

What can i do server side?

 

[Bitpalast]

This is solely a client issue. When the client still uses an expired root certificate, the validity of Let's Encrypt certificates cannot be checked. The check will always fail. For that reason you are seeing this issue only on that very one client. You need to update the root certificates on the client. This is normally done by an operating system update, e.g. an Android upgrade.

 

[RobertoMa]

This is solely a client issue. When the client still uses an expired root certificate, the validity of Let's Encrypt certificates cannot be checked. The check will always fail. For that reason you are seeing this issue only on that very one client. You need to update the root certificates on the client. This is normally done by an operating system update, e.g. an Android upgrade.

My device has last version of Android.

 

[Bitpalast]

Have you considered to ask Spark support about it?

 

[RobertoMa]

Have you considered to ask Spark support about it?

Yes. They said the root certificates.

 

[RobertoMa]

I solved it by putting the reverse ip as the mx record.