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 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.

Thanks @md-misko - I’ve merged the PR and bumped the discourse/mail-reciever:release tag on Dockerhub. I’m sure you’re already aware, but in case anyone else comes across this topic, you can update your mail receiver version by running: docker pull discourse/mail-receiver:release cd /var/discourse ./launcher rebuild mail-receiver

have you tried these steps [imagem] Let's Encrypt X3 nightmare Support Can you try docker pull discourse/mail-receiver:release cd /var/discourse ./launcher rebuild mail-receiver

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?

[imagem] RGJ: Postfix is happily running and accepting mails after that 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! [imagem] RGJ: Sometimes the logs don’t seem to flush immediately so you might need to wait for a while before you get some output. 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).

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 : /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 repeated six more times: Single line of log entries without line breaks.............................................................................................................................................................................................. I was only looking at the end of the output, and there was always seemingly just the without any other entries. Definitely something wrong with the rendering of the log via ./launcher logs mail-receiver.

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 Dockerfile main FROM debian:bookworm-slim ARG INCLUDE_DMARC=true ENV INCLUDE_DMARC=${INCLUDE_DMARC} RUN DEBIAN_FRONTEND=noninteractive apt update \ && DEBIAN_FRONTEND=noninteractive apt install -y --no-install-recommends curl perl postfix ruby socat \ && if [ "$INCLUDE_DMARC" = "true" ]; then \ DEBIAN_FRONTEND=noninteractive apt install -y --no-install-recommends opendmarc opendkim opendkim-tools postfix-policyd-spf-python; \ fi \ && DEBIAN_FRONTEND=noninteractive apt -y --purge autoremove \ && DEBIAN_FRONTEND=noninteractive apt clean EXPOSE 25 VOLUME /var/spool/postfix RUN >/etc/postfix/main.cf \ && postconf -e maillog_file=/dev/stdout \ && postconf -e smtputf8_enable=no \ && postconf -e compatibility_level=2 \ This file has been truncated. show original RUN >/etc/postfix/main.cf \ + && postconf -e maillog_file=/dev/stdout \ && postconf -e smtputf8_enable=no \ ...

[imagem] md-misko: I believe I figured this one out, there is a maillog_file line missing in the Dockerfile 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?

https://github.com/discourse/mail-receiver/pull/12 [imagem] Mail-receiver loses IP to hostname resolution after recent upgrade and prevents anti-spam measures from working Support https://github.com/discourse/mail-receiver/pull/12 @david This should fix both issues mentioned in Self-hosted mail-receiver update following Let's Encrypt root certificate change - #6 by md-misko Please evaluate whether removing postfix from the chroot jail introduces any security issues (IMO it shouldn’t, as postfix is already isolated inside a dedicated docker image).

Have you got any ideas of how to test that the current running image is running the latest version?

A little convoluted… but I think this should work: # First, make sure you've got the latest base image locally docker pull discourse/mail-receiver:release # Get the top layer of the base image BASE_IMAGE_HASH=$(docker history discourse/mail-receiver:release -q | head -n 1) # Get the layers of the **running** version RUNNING_IMAGE_HASH=$(docker container inspect mail-receiver -f "{{.Image}}") RUNNING_IMAGE_LAYERS=$(docker history $RUNNING_IMAGE_HASH -q) # Check if the running image layers include the current base image: [[ "$RUNNING_IMAGE_LAYERS" == *"$BASE_IMAGE_HASH"* ]] && echo "Up to date" That will print “Up to date” if you’re up to date. Otherwise, the final line will print nothing, and exit with a non-zero status.

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

Suporte ao Produto

md-misko 7 Dezembro , 2021 14:43 9

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

Tópico		Respostas	Vistas
Self-hosted mail-receiver update following Let's Encrypt root certificate change Self-hosting mail-receiver , letsencrypt	12	2810	10 Fevereiro , 2022
Let's Encrypt X3 nightmare Product Support	12	1753	1 Outubro , 2021
Mail-receiver loses IP to hostname resolution after recent upgrade and prevents anti-spam measures from working Product Support	2	1048	7 Dezembro , 2021
Email receive issue Bug mail-receiver , fixed	29	1385	13 Abril , 2026
Mail-receiver won’t deliver mail to Discourse Self-hosting mail-receiver	16	731	26 Janeiro , 2023

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

Related topics