I’m getting the following error when using the mail-receiver app as of today. It was working fine before. It’s trying to send the e-mail to Discourse via API. Is it possible it’s caused by DST Root CA X3 certificate expiration? If yes, anyone has any idea about how to solve it? I tried to rebuild …

Thanks for the report @wlandgraf - we’ll get a new mail-receiver image pushed up to Dockerhub ASAP

The release tag on Dockerhub has now been updated. Assuming you followed the official setup instructions, you can pull the new image by running cd /var/discourse ./launcher rebuild mail-receiver https://hub.docker.com/layers/discourse/mail-receiver/release/images/sha256-67222bded8651b2aefae113c57f…

Hi @david , your prompt response is really appreciated. However, that didn’t solve my problem. It still persists.

In /var/discourse/containers/mail-receiver.yml, what do you have on the base_image: line? It should be: base_image: discourse/mail-receiver:release (More info on that here )

This is the beginning of my file: ## this is the incoming mail receiver container template ## ## After making changes to this file, you MUST rebuild ## /var/discourse/launcher rebuild mail-receiver ## ## BE *VERY* CAREFUL WHEN EDITING! ## YAML FILES ARE SUPER SUPER SENSITIVE TO MISTAKES IN WHITESPA…

Can you try docker pull discourse/mail-receiver:release cd /var/discourse ./launcher rebuild mail-receiver

That did it! Thank you very much! A few questions if you don’t mind: Why was that necessary? Should I always manually pull the latest image before building? Do I have to apply the same procedure (docker pull) when rebuilding the app? I see e-mails sent after the rebuild arrived, but not the e-mail…

It looks like your docker installation had cached the :release tag. To avoid the need for a docker pull in future, we might be able to add some logic to our launcher script. The app images are handled differently, so there won’t be any caching issue there. Emails sent during the outage should have…

Excelent. Thank you again for the fast response. The world seems to be suffering from this Root CA X3 mess, you have now made your contribution to make the world a little bit better now. :smiley:

كابوس Let's Encrypt X3

الدعم

wlandgraf (Wagner Landgraf) 30 سبتمبر 2021، 11:50م 11

ممتاز. شكراً جزيلاً مرة أخرى على الاستجابة السريعة. يبدو أن العالم يعاني من فوضى شهادة Root CA X3، وقد أسهمت الآن في جعل العالم أفضل قليلاً.

3 إعجابات

الموضوع		الردود	مرات العرض
Self-hosted mail-receiver update following Let's Encrypt root certificate change Self-hosting mail-receiver , letsencrypt	12	2449	10 فبراير 2022
Mail-receiver log errors after letsencrypt update Support	13	1507	8 ديسمبر 2021
Direct-delivery email certificate error Support	7	988	10 مارس 2022
Replying through email suddenly stopped due to Let's Encrypt changes Support	4	997	12 يناير 2022
Mail-receiver won’t deliver mail to Discourse Self-hosting mail-receiver	16	390	26 يناير 2023

كابوس Let's Encrypt X3

الموضوعات ذات الصلة