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

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…

have you tried these steps [imagen] 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?

[imagen] 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 (us…

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

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

[imagen] 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/11

https://github.com/discourse/mail-receiver/pull/12 [imagen] 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 …

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…

Errores de registro de mail-receiver después de la actualización de letsencrypt

Soporte

IAmGav (Gavin Perch) 1 Octubre, 2021 06:53 2

¿Has probado estos pasos?

1 me gusta

Tema		Respuestas	Vistas
Self-hosted mail-receiver update following Let's Encrypt root certificate change Self-hosting mail-receiver , letsencrypt	12	2456	10 Febrero 2022
Let's Encrypt X3 nightmare Support	13	1519	2 Octubre 2021
Mail-receiver loses IP to hostname resolution after recent upgrade and prevents anti-spam measures from working Support	3	954	7 Diciembre 2021
Email receive issue Bug mail-receiver , fixed	30	423	13 Abril 2026
Mail-receiver won’t deliver mail to Discourse Self-hosting mail-receiver	16	399	26 Enero 2023

Errores de registro de mail-receiver después de la actualización de letsencrypt

Temas relacionados