I'm currently testing the following workaround:
--- /usr/lib/postfix/configure-instance.sh.orig 2016-11-14
09:24:03.832342133 +0200
+++ /usr/lib/postfix/configure-instance.sh 2016-11-14 09:19:20.336826008
+0200
@@ -120,6 +120,8 @@
if [ -f /${file} ]; then rm -f ${file} && cp /${file} ${file}; fi
if [ -f ${file} ]; then chmod a+rX ${file}; fi
done
+ # an empty resolv.conf is useless -- ubuntu bug LP: #1519331
+ grep -q nameserver etc/resolv.conf || echo nameserver 127.0.1.1 >>
etc/resolv.conf
# ldaps needs this. debian bug 572841
(echo /dev/random; echo /dev/urandom) | cpio -pdL --quiet . 2>/dev/null
|| true
rm -f usr/lib/zoneinfo/localtime
It seems to work for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1519331
Title:
Postfix cannot resolve DNS if network was unavailable when it was
started, such as on a laptop
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1519331/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
