Hi, thank you for reporting this issue and the pre-analysis. I wonder why the After=network.target in the service isn't protecting this enough.
Since you already checked so much, could you outline which script is doing the copy of resolv.conf on postfix initialization? That should be the one that would be supposed to run "later" once all of the network is ready. Also finally since you are referring to systemd - are you testing Xenial or Yakkety? I prepped already a bit of a trivial repro case: lxc launch images:ubuntu/yakkety/amd64 test-pf lxc exec test-pf apt-get update # choose the simple local only config lxc exec test-pf apt-get install postfix lxc exec test-pf reboot lxc exec test-pf ls -laF /var/spool/postfix/etc/ lxc exec test-pf cat /var/spool/postfix/etc/resolv.conf # 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 lxc exec test-pf cat /etc/resolv.conf # 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 nameserver 10.0.4.1 search lxd With that I see the "old" content of resolv.conf prior to it being updated. Is that enough in your opinion as recreation of the case? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1627117 Title: After systemd integration enabled, Postfix will no longer send mail on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1627117/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
