A couple weeks ago I suddenly stopped being able to access my email from my phone. When I tried I got a message that the server identity could not be verified. When I cluck on details it tells me the denial is issued from Let’s Encrypt. Can anyone help me with restoring my email access? I don’t know where Let’s Encrypt came form or why it’s blocking my emails but it’s a real pain.
Let’s Encrypt has nothing to do with your mail delivery or access, and is not blocking anything. If a security certificate issued by Let’s Encrypt (or any other CA) has expired, the mail client on your phone may be giving warnings. What, exactly, do the “details” say?
Is this webmail hosted by yourself? Or some other party? If the latter is the case, you should contact that other party of your problem, as it most likely is a configuration problem on their end.
The details say “ssl.server293.com Issued by Let’s Encrypt Authority…Not Trusted Expires 8/26/17” When I click on More Details it gives me a bunch of information but under “Issuer Name” the organization is Let’s Encrypt Authority X3. Thanks for helping me out!
It’s hosted by some other party, but it has been for several years and this just popped up recently. I’ll check with them, though, in case they changed something on their end that’s causing this. Thanks for your help!
Hi @user2, this error is usually caused by the e-mail host choosing to use Let’s Encrypt certificates, but then forgetting to renew them. Renewing the certificate is mandatory, but it’s possible for the host to forget to do it. Only the host can perform this renewal; Let’s Encrypt itself can’t do anything to fix it without the host’s involvement.
It’s possible that the host had switched from some other certificate provider to Let’s Encrypt because Let’s Encrypt certificates are free of charge. But Let’s Encrypt certificates have to be renewed more frequently than some other certificates do, so it might be easier for people to forget about the mandatory renewals.
It looks like the certificate is not expired, and was probably issued in late May (i.e., a couple weeks ago). I'm guessing the problem is one of these:
Missing intermediate certificate
Phone does not include DST Root X3 in its trust store.
@user2, can you tell us what model of phone, and most importantly what version of the operating system you are running, and what software you normally use to access your email?
@user2, the host should still probably be in a position to fix the problem, but I agree that the problem is not exactly what I thought. Per @jsha’s suggestions, It could be that the host configured the certificate incorrectly when installing it, or that your phone isn’t compatible with Let’s Encrypt certificates.
This shows that intermediate certificate is correctly included, so most likely the problem is that your phone does not include DST Root X3. The answers to my questions above would still be useful. You can also check the compatibility list at https://letsencrypt.org/docs/certificate-compatibility/.
Can’t tell if it is sending the intermediate chain info…
or if your phone doesn’t like that they prefer DHE ciphers but offer them via only DH 1024:
subject=/CN=ssl.server293.com
issuer=/C=US/O=Let’s Encrypt/CN=Let’s Encrypt Authority X3
No client certificate CA names sent
Peer signing digest: SHA512 Server Temp Key: DH, 1024 bits
SSL handshake has read 3846 bytes and written 399 bytes
Verification error: unable to get local issuer certificate