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 :upside_down_face:) 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

[תמונה] 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 Self-hosting This announcement only affects self-hosters who are running Configure direct-delivery incoming email for self-hosted sites with Mail-Receiver. 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. 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!

Do you have your own mail-receiver set up? If so you could try a rebuild: cd /var/discourse ./launcher rebuild mail-receiver

התגובה דרך המייל הופסקה פתאום עקב שינויים ב-Let's Encrypt

תמיכה

PeterClamp (Peter Clamp) 12 בינואר,‏ 2022,‏ 3:53pm 4

Thank you - this worked!

נושא		תגובות	צפיות
Self hosted Reply by Email stopped working after latest update Product Support	25	2611	26 באוקטובר,‏ 2021
Reply by email stops working Product Support	1	431	16 בספטמבר,‏ 2021
Incoming mail server has certificate error Self-hosting	13	1027	7 באוקטובר,‏ 2022
Self-hosted mail-receiver update following Let's Encrypt root certificate change Self-hosting mail-receiver , letsencrypt	12	2824	10 בפברואר,‏ 2022
Let's Encrypt X3 nightmare Product Support	12	1757	1 באוקטובר,‏ 2021

התגובה דרך המייל הופסקה פתאום עקב שינויים ב-Let's Encrypt

נושאים קשורים