Atualização do mail-receiver auto-hospedado após alteração no certificado raiz Let's Encrypt

Instalação
,
1

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 expiration. Unfortunately we missed the public mail-receiver docker image, which has not been updated for a few months.

This means that existing self-hosted mail-receiver installations will be unable to deliver mail to letsencrypt-secured sites.

We just pushed an updated version to DockerHub, which includes the new root certificate. Assuming you followed the official installation instructions, you can update your installation by running

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

Mails received by broken installations will have been temporarily queued on the sending server. Those servers should attempt to redeliver the mail periodically, so any missed mails should arrive soon after you update the image.

If you’re still seeing issues after following these steps, make sure you’re running the release version of mail-receiver. You can find information on that in this topic.

Sorry for the disruption here! Big thanks to @wlandgraf for initially reporting the issue, and helping us test the fix :heart:

28 curtidas
2

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
error: Your local changes to the following files would be overwritten by merge:
	templates/web.letsencrypt.ssl.template.yml
Please commit your changes or stash them before you merge.
Aborting
failed to update
1 curtida
3

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

3 curtidas
4

Ah, I did make a change :innocent: I got it to upgrade now, thanks!

2 curtidas
5

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.

7 curtidas
6

@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 figure out what the root issue is, but I don’t have deep enough knowledge of postfix to figure it out. I found similar reports (client=unknown even when PTR record exists in DNS) regarding postfix in a chroot jail, so this might have something to do with it. Also, dnsutils seem to be missing from the new mail-receiver Debian image, but installing them still doesn’t fix the issue?

This one should be fixed easily:

4 curtidas
7

@david Obrigado por esta correção! Acabei de executá-la e consigo ver que está funcionando. :+1:

Existe alguma maneira de ver quais e-mails não puderam ser entregues desde 1º de outubro?

Tentei isto, mas só vejo 5 solicitações (a mais antiga foi recebida em 26 de novembro):

/var/discourse/launcher enter mail-receiver
mailq

Também tentei olhar os logs, mas só obtive o aviso relatado aqui:

3 curtidas
8

Acho que qualquer coisa que ainda não esteja na fila deveria ter sido devolvida ao remetente. Receio não ter certeza se o contêiner possui logs que remontem a um período anterior ao que você encontrou.

4 curtidas
9

Simplesmente adicionar pull_image após a linha 657 resolveria a necessidade de puxar explicitamente a imagem antes da reconstrução? Ou seja:

  # Se a imagem que está sendo inicializada não for a imagem base do Discourse
  if [[ ! X"" = X"$base_image" ]]; then
    image=$base_image
    # Tenta atualizar a imagem
    pull_image
  fi

Isso fará com que um docker pull $image sempre aconteça durante a inicialização/reconstrução de um contêiner com base_image definido em seu arquivo yml. Não acho que isso prejudique o mail-receiver se ele já estiver atualizado, mas não tenho certeza se há outras situações em que isso poderia ser um problema.

2 curtidas
10

Sim, um pull incondicional provavelmente faz sentido aqui. É um pouco estranho que ele se aplique apenas à nossa imagem base principal no momento. O que você acha, @Falco?

2 curtidas
11

Eu estaria interessado em ouvir uma resposta definitiva para esta pergunta :slight_smile:

1 curtida
12

Eu acho que você pode ver isso consultando a tabela incoming_emails do postgres

2 curtidas
13

Infelizmente, isso não mostra nada no período relevante (outubro de 2021 a fevereiro de 2022).

Haveria algum log no próprio container do receptor de e-mail?

1 curtida