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 ce…

Thanks for the fix! My update got stuck with the following error message. I haven’t made any changes to this template, so I’m not sure what to do? root@ba /var/discourse # ./launcher rebuild mail-receiver Ensuring launcher is up to date Fetching origin Updating Launcher... Updating 46d899f..990519e…

What happens if you cd /var/discourse git diff Does it show any differences in the web.letsencrypt.ssl.template.yml file? If so, you can reset them using git reset --hard

[이미지] david: git diff Ah, I did make a change :innocent: I got it to upgrade now, thanks!

You can test whether you’re running the old mail-receiver like this. docker exec mail-receiver bash -c "cat /etc/issue|grep Alpine" If it’s Alpine, it’s the old one. docker exec mail-receiver bash -c "cat /etc/issue|grep 'Debian GNU/Linux 11'" If it’s Debian, it’s the new one.

@david , would you mind having a look at the issues below, the latest update to the mail-receiver removed the ability to implement additional anti-spam measures, which worked wonders in the previous version, and my forum is under increasing spam pressure again due to the last change. I tried to figu…

I think anything which isn’t still in the queue should have been bounced back to the sender. I’m afraid I’m not sure whether the container has any logs which would go back further than what you’ve found.

launcher 7c9b93a9c run_bootstrap() { # Is the image available? # If not, pull it here so the user is aware what's happening. $docker_path history $image >/dev/null 2>&1 || pull_image set_template_info …

Yeah, an unconditional pull probably makes sense here. It’s a little strange that it only applies to our main base image at the moment. What do you think @Falco ?

Nacho Caballero: Is there a way to see which emails were not able to be delivered since October 1st? I’d be interested to hear a definitive answer to this question :slight_smile:

Let's Encrypt 루트 인증서 변경에 따른 자체 호스팅 메일 수신기 업데이트

지원 자체 호스팅

Nacho_Caballero (Nacho Caballero) 11월 30, 2021, 7:59오전 7

@david Thanks for this fix! I just ran it and I can see it’s working.

Is there a way to see which emails were not able to be delivered since October 1st?

I’ve tried this, but I only see 5 requests (the earliest was received on Nov 26):

/var/discourse/launcher enter mail-receiver
mailq

I also tried looking at the logs, but I only got the warning reported here:

글		댓글	조회수
Let's Encrypt X3 nightmare Support	12	1618	10월 1, 2021
Mail-receiver log errors after letsencrypt update Support	12	1621	12월 8, 2021
Mail-receiver loses IP to hostname resolution after recent upgrade and prevents anti-spam measures from working Support	2	997	12월 7, 2021
Direct-delivery email certificate error Support	6	1058	2월 8, 2022
Update mail-receiver to the release version Sysadmins how-to	8	3140	1월 1, 2020

Let's Encrypt 루트 인증서 변경에 따른 자체 호스팅 메일 수신기 업데이트

Related topics