# Replying through email suddenly stopped due to Let's Encrypt changes
**URL:** https://meta.discourse.org/t/replying-through-email-suddenly-stopped-due-to-lets-encrypt-changes/214540
**Category:** Support
**Created:** [January 11, 2022, 3:15pm UTC](https://meta.discourse.org/t/replying-through-email-suddenly-stopped-due-to-lets-encrypt-changes/214540 "2022-01-11T15:15:38Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@PeterClamp](https://meta.discourse.org/u/PeterClamp)
#### Post date: [January 11, 2022, 3:15pm UTC](https://meta.discourse.org/t/replying-through-email-suddenly-stopped-due-to-lets-encrypt-changes/214540/1 "2022-01-11T15:15:38Z")
Hi, we’re unfortunately having some issues with the “reply by email” part of Discourse…
**Context:**
Since we started using Discourse nearly 2 years ago it has been great for our network to use as a comms platform. People would post \> everyone would be emailed notifying of that post \> then people could either go on to the topic and reply in Discourse OR people could simply hit reply in their inbox and their reply would be posted as a reply in the topic on Discourse. The author of the post would also be notified that someone had replied.
**Problem:**
Recently the replying in our inbox ability has stopped! We cannot work out why… (Not exactly tech whizzes here 🙃)
People are hitting reply and either:
- Getting bounces
- Nothing happening
Either way, _ **the author is not seeing any replies on the post or being notified of any replies** _.
**Things to note:**
- SOME emails sent from Discourse about an original post are coming from a “Name (noreply@forum.[ourdomain].com)” which I don’t know how to change
- The email layout we have in our inboxes and in Discourse settings is "replies+######@forum.[ourdomain].com and as both match it should surely work? (Where#### represents a lot of numbers and letters).
- We have 0 emails in since 30th September 2021, but plenty before then - hence sudden stop. (Under “Admin - emails - received”)
- We have had 0 rejected from within Discourse (Under “admin - emails - rejected”)
Is this enough to explain the problem?
Hopefully someone out there can help us!
Cheers,
Peter
---
### Author:  [@JammyDodger](https://meta.discourse.org/u/JammyDodger)
#### Post date: [January 11, 2022, 4:02pm UTC](https://meta.discourse.org/t/replying-through-email-suddenly-stopped-due-to-lets-encrypt-changes/214540/2 "2022-01-11T16:02:55Z")
Do you have your own [mail-receiver](https://meta.discourse.org/t/direct-delivery-incoming-email-for-self-hosted-sites/49487) set up? If so you could try a rebuild:
```plaintext
cd /var/discourse
./launcher rebuild mail-receiver
```
---
### Author:  [@david](https://meta.discourse.org/u/david)
#### Post date: [January 11, 2022, 4:05pm UTC](https://meta.discourse.org/t/replying-through-email-suddenly-stopped-due-to-lets-encrypt-changes/214540/3 "2022-01-11T16:05:22Z")
> [@PeterClamp](#):
>
> since 30th September 2021,
The timing suggests this is almost certainly caused by the letsencrypt certificate changes. You can find instructions for fixing the problem here:
> [@Self-hosted mail-receiver update following Let's Encrypt root certificate change](https://meta.discourse.org/t/self-hosted-mail-receiver-update-following-lets-encrypt-root-certificate-change/204924):
>
> This announcement only affects self-hosters who are running [Configure direct-delivery incoming email for self-hosted sites with Mail-Receiver](https://meta.discourse.org/t/direct-delivery-incoming-email-for-self-hosted-sites/49487). Managed hosting customers, and self-hosters using POP3 for incoming mail are not affected. As you may be aware, Let’s Encrypt recently [changed their root certificate](https://letsencrypt.org/docs/dst-root-ca-x3-expiration-september-2021/). The old root certificate expired today, and has caused a number of issues for out-of-date clients across the web. All of our systems at CDCK are up-to-date, and were not affected by today’s…
Unfortunately there was no way for us to push out an automatic update for this problem, so an “Announcement” was the best we could do - sorry for the disruption!
---
### Author:  [@PeterClamp](https://meta.discourse.org/u/PeterClamp)
#### Post date: [January 12, 2022, 3:53pm UTC](https://meta.discourse.org/t/replying-through-email-suddenly-stopped-due-to-lets-encrypt-changes/214540/4 "2022-01-12T15:53:47Z")
Thank you - this worked!
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [February 11, 2022, 3:53pm UTC](https://meta.discourse.org/t/replying-through-email-suddenly-stopped-due-to-lets-encrypt-changes/214540/5 "2022-02-11T15:53:59Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.