Package: postfix Version: 3.1.4-4 Followup-For: Bug #854475 Dear Maintainer,
I found a bug that is probably related to #854475 because it seems also to be caused by postfix starting too early. I have several systems where mail gets stuck in the queue with "(Host or domain name not found. Name service error for name=XXXXXXXX type=AAAA: Host not found, try again)". Turns out /var/spool/postfix/etc/resolv.conf is empty, only containing the empty template " Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN " from resolvconf. But /etc/resolv.conf itself contains proper nameserver entries as configured in /etc/network/interfaces. So outgoing emails are stuck in the queue until I restart postfix and /var/spool/postfix/etc/resolv.conf gets updated. With "After=network.target" applied, postfix start is delayed and the postfix copy of resolv.conf contains the necessary entries. Best regards, Marcus Jodorf -- System Information: Debian Release: 9.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
