Network connectivity is fine when this problem occurs (I read my mail via IMAP w/o local message body cache from the same server used as smart host, use SSH to other hosts, and surf the web - I never noticed network problems when the postfix mail delivery did not work). It seems, postfix either does not retry name resolution, or somehow name resolution fails for postfix, but not other programs. When I manually check host name resolution, it works fine. Name service error for name=XXXXXXXX type=AAAA: Host not found, try again) The local postfix does not receive outside mail. I use postfix to deliver all sent mail to the company SMTP server.
I detect this problem after wandering about no answers to my emails, or by checking the current mail queue, which should be empty when I am at the office. target should always be reached at boot, regardless of whether using ifupdown, network-manager, or networkd, and the only difference is that postfix startup will be delayed a short while until the network is fully configured.Įvery now and then postfix installed on my laptop stops delivering mails. target, if the system fails to reach this target postfix will not start, which would be a serious regression. This is highly unlikely, as a hard dependency on an SMTP service is unusual.īecause the postfix service will now depend on network- online. d'īecause we are changing the order of service initialization at boot, if there are other packages which have undeclared dependencies on postfix (or generically, on a running SMTP server), these services may now fail a race with postfix startup where they succeeded before. conf & sudo rmdir -p /etc/systemd/ system/ systemd- resolved. conf match.Ĩ Run 'sudo rm -f /etc/systemd/ system/ systemd- resolved. Confirm that /etc/nf and /var/spool/ postfix/ etc/resolv. d echo -e ' \nExecStartPre= /bin/sleep 20' | sudo tee /etc/systemd/ system/ systemd- resolved. Run 'sudo mkdir -p /etc/systemd/ system/ systemd- resolved.
#Debian use systemd monitor postfix install#
Install postfix on a machine or container (not chroot) in the default configuration.Ģ. Race condition between resolvconf and postfix on startup leaves postfix with a different DNS server configuration in its chroot than is used on the host system, which may cause it to experience DNS resolution errors.ġ.
0 kommentar(er)
