Thunderbird not getting mail after certificate expiry/renewal

Help
1

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is: tecreations.ca

I ran this command: automated certbot as configured by certbot

It produced this output: n/a

My web server is (include version): apache 2 / thunderbird (auto-updated)

The operating system my web server runs on is (include version): ubuntu 16.04

My hosting provider, if applicable, is: digital ocean

I can login to a root shell on my machine (yes or no, or I don't know): yes

I'm using a control panel to manage my site (no, or provide the name and version of the control panel): no

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): 0.31.0

Hello, after Certbot renewed my certificate (for the webserver), email services fail to work. My email configuration points to the certifcate and chain in /etc/letsencrypt/live/tecreations.ca/*.

Does the newer version of Certbot with Apache use different locations? SSL/TLS on Apache is still working correctly.

Thanks

2

No, the folder layout is the same with your very old version and newer versions

Your most recent cert was different than the one before that. The latest cert just has the apex domain in it. Your previous cert had that and a www subdomain. Could this be causing your mail problems?

What does this show?

sudo certbot certificates

image
image1971×690 64.1 KB

4 Likes
3

Thunderbird is an email client - not an email server.
Which system is using which cert?
Have you restarted the email server?

4 Likes
4

:flushed:

You should probably look this over after you update your certificate.

https://ubuntu.com/about/release-cycle

5 Likes
5

Hi, it shows this, but I guess it just needed the server to be restarted.

tim@tecreations:~$ sudo certbot certificates
[sudo] password for tim:
Saving debug log to /var/log/letsencrypt/letsencrypt.log

Found the following certs:

Certificate Name: tecreations.ca-0001
Domains: tecreations.ca
Expiry Date: 2025-01-08 22:51:59+00:00 (VALID: 78 days)
Certificate Path: /etc/letsencrypt/live/tecreations.ca-0001/fullchain.pem
Private Key Path: /etc/letsencrypt/live/tecreations.ca-0001/privkey.pem

Certificate Name: tecreations.ca
Domains: tecreations.ca www.tecreations.ca
Expiry Date: 2024-12-05 00:10:43+00:00 (VALID: 43 days)
Certificate Path: /etc/letsencrypt/live/tecreations.ca/fullchain.pem
Private Key Path: /etc/letsencrypt/live/tecreations.ca/privkey.pem

Could the change from www to the apex domain also cause issues with Spring SSL also?

Thanks,

Tim

1 Like
6

Hi,

I have Apache 2 and Thunderbird using it, as well, I had a Spring Java keystore working, but after an updated certificate and recreating the keystore, it failed in Chrome for the Spring Security login.

Rebooting fixed it. Thank you.

Tim

1 Like
7

The first cert doesn't seem necessary.
[the second cert contains that name + "www"]

3 Likes