Erreurs de journal Mail-receiver après la mise à jour de letsencrypt

Soutien
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 « J'aime »
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 « J'aime »
9

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

10

Merci @md-misko - j’ai fusionné la PR et mis à jour l’étiquette discourse/mail-reciever:release sur Dockerhub.

Je suis sûr que vous êtes déjà au courant, mais au cas où quelqu’un d’autre tomberait sur ce sujet, vous pouvez mettre à jour votre version du récepteur de courrier en exécutant :

docker pull discourse/mail-receiver:release
cd /var/discourse
./launcher rebuild mail-receiver
3 « J'aime »
11

Avez-vous des idées sur la façon de tester que l’image en cours d’exécution est la dernière version ?

12

Un peu alambiqué… mais je pense que cela devrait fonctionner :

# Tout d'abord, assurez-vous d'avoir la dernière image de base localement
docker pull discourse/mail-receiver:release

# Obtenez la couche supérieure de l'image de base
BASE_IMAGE_HASH=$(docker history discourse/mail-receiver:release -q | head -n 1)

# Obtenez les couches de la version **en cours d'exécution**
RUNNING_IMAGE_HASH=$(docker container inspect mail-receiver -f "{{.Image}}")
RUNNING_IMAGE_LAYERS=$(docker history $RUNNING_IMAGE_HASH -q)

# Vérifiez si les couches de l'image en cours d'exécution incluent l'image de base actuelle :
[[ "$RUNNING_IMAGE_LAYERS" == *"$BASE_IMAGE_HASH"* ]] && echo "À jour"

Cela affichera “À jour” si vous êtes à jour. Sinon, la dernière ligne n’affichera rien et se terminera avec un statut non nul.

2 « J'aime »
13

Oh. C’est génial. Et il semble que ce soit une solution générale pour laquelle je n’avais trouvé que des solutions ponctuelles auparavant. Il m’aurait fallu un certain temps pour comprendre cela. Le RUNNING_IMAGE_LAYERS est ce que je ne savais pas chercher.

Je l’ai testé sur une instance qui avait été mise à niveau et une autre qui ne l’avait pas été, et il semble que le comportement soit celui attendu.

Merci beaucoup !

3 « J'aime »
14

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