Erros de log do Mail-receiver após atualização do letsencrypt

Suporte
1

Continuing the discussion from Self-hosted mail-receiver update following Let's Encrypt root certificate change:

After updating mail-receiver to latest ./launcher logs mail-receiver errors out after

postfix/postfix-script: warning: symlink leaves directory: /etc/postfix/./makedefs.out
<20>Oct  1 06:10:33 postfix/postfix-script[86]: warning: symlink leaves directory: /etc/postfix/./makedefs.outStarting Postfix

and doesn’t show any other events (incoming emails, rejected emails, …).

I’ve encountered some issues with custom postfix settings (which worked flawlessly prior to recent update) and need to debug, which is difficult without logs.

2

have you tried these steps

1 curtida
3

I do see the same errors warnings but Postfix is happily running and accepting mails after that.

Sometimes the logs don’t seem to flush immediately so you might need to wait for a while before you get some output. But that’s unrelated to the warnings.

So is it actually crashing for you?

4

Ditto, with vanilla settings. But I had to temporarily disable additional postfix rule

  POSTCONF_smtpd_client_restrictions: 'regexp:/etc/postfix/shared/client_access_regex'

which worked perfectly before the upgrade (uses regex rules to reject spammers). The real issue is that with this setting enabled, postfix starts rejecting all incoming email, but I can’t see why from the logs!

A while maybe, but it’s been hours and still nothing in logs (neither accepted nor rejected emails are shown, and there is inbound traffic).

5

You were right, there are other log entries in the output, but the output itself is garbled:

./launcher logs mail-receiver output begins with a <HEAD>:

/bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
Operating environment:
HOSTNAME=discourse-mail-receiver
LANGUAGE=en_US.UTF-8
MAIL_DOMAIN=...
...
...
Setting smtpd_tls_security_level to 'may'
postfix/postfix-script: warning: symlink leaves directory: /etc/postfix/./makedefs.out

followed by a single line of log entries, and ending with the <HEAD> repeated six more times:

<HEAD>
Single line of log entries without line breaks..............................................................................................................................................................................................
<HEAD>
<HEAD>
<HEAD>
<HEAD>
<HEAD>
<HEAD>

I was only looking at the end of the output, and there was always seemingly just the <HEAD> without any other entries.

Definitely something wrong with the rendering of the log via ./launcher logs mail-receiver.

6

I believe I figured this one out, there is a maillog_file line missing in the Dockerfile. Temp fix: added

  POSTCONF_maillog_file: '/dev/stdout'

to mail-receiver.yml and rebuilt, but this should probably be fixed in the docker image

RUN >/etc/postfix/main.cf \
+	&& postconf -e maillog_file=/dev/stdout \
	&& postconf -e smtputf8_enable=no \
...
7

So after adding this, the error is gone, and the logs are working? If so, would you mind submitting a PR to make that change?

8
1 curtida
9

https://github.com/discourse/mail-receiver/pull/12

10

Obrigado @md-misko - Eu mesclei o PR e atualizei a tag discourse/mail-reciever:release no Dockerhub.

Tenho certeza de que você já está ciente, mas caso alguém mais encontre este tópico, você pode atualizar sua versão do receptor de e-mail executando:

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

Você tem alguma ideia de como testar se a imagem em execução atual está executando a versão mais recente?

12

Um pouco complicado… mas acho que isso deve funcionar:

# Primeiro, certifique-se de ter a imagem base mais recente localmente
docker pull discourse/mail-receiver:release

# Obtenha a camada superior da imagem base
BASE_IMAGE_HASH=$(docker history discourse/mail-receiver:release -q | head -n 1)

# Obtenha as camadas da versão **em execução**
RUNNING_IMAGE_HASH=$(docker container inspect mail-receiver -f "{{.Image}}")
RUNNING_IMAGE_LAYERS=$(docker history $RUNNING_IMAGE_HASH -q)

# Verifique se as camadas da imagem em execução incluem a imagem base atual:
[[ "$RUNNING_IMAGE_LAYERS" == *"$BASE_IMAGE_HASH"* ]] && echo "Atualizado"

Isso imprimirá “Atualizado” se você estiver atualizado. Caso contrário, a última linha não imprimirá nada e sairá com um status diferente de zero.

2 curtidas
13

Ah. Isso é brilhante. E parece ser uma solução geral para a qual eu anteriormente só encontrava soluções pontuais. Levaria um tempo para eu descobrir isso. O RUNNING_IMAGE_LAYERS é o que eu não sabia que deveria procurar.

Testei em uma instância que havia sido atualizada e em uma que não havia sido, e parece se comportar como esperado.

Muito obrigado!

3 curtidas
14

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.