Your message dated Thu, 25 May 2017 22:44:26 +0200
with message-id <[email protected]>
and subject line Re: Bug#853267: Copies empty resolv.conf into chroot if
resolvconf is in use
has caused the Debian Bug report #853267,
regarding Copies empty resolv.conf into chroot if resolvconf is in use
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
853267: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853267
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: postfix
Version: 3.1.4-3
Severity: important
Hi,
my fairly standard Debian stretch installation that uses resolvconf with
dns-* configuration lines in /etc/network/interfaces reproducibly does
start a postfix instance at boot unable to deliver any mail to an
external destination.
Jan 30 13:56:32 voiptest postfix/error[49391]: 5B33E1621E:
to=<[email protected]>, relay=none, delay=2128, delays=2128/0.03/0/0,
dsn=4.4.3, status=deferred (delivery temporarily suspended: Host or
domain name not found. Name service error for name=xxx.lrz.de
type=MX: Host not found, try again)
The reason is that an empty resolv.conf is copied into the chroot
root@voiptest:~# cat /etc/network/interfaces
# The primary network interface
auto eth0
iface eth0 inet static
[...]
dns-nameservers 10.156.33.53 129.187.5.1
dns-search lrz.de srv.lrz.de srv.mwn.de ws.lrz.de
root@voiptest:~# 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.156.33.53
nameserver 129.187.5.1
search lrz.de srv.lrz.de srv.mwn.de ws.lrz.de
root@voiptest:~# 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
probably because postfix starts too early.
Adding
===
After=resolvconf.service
===
to /etc/systemd/system/postfix.service.d/override.conf seems to fix
this problem.
Bernhard
--- End Message ---
--- Begin Message ---
Version: 3.1.4-7
On 22.05.2017 21:17, Scott Kitterman wrote:
>> my fairly standard Debian stretch installation that uses resolvconf with
>> dns-* configuration lines in /etc/network/interfaces reproducibly does
>> start a postfix instance at boot unable to deliver any mail to an
>> external destination.
>>
>>
>> The reason is that an empty resolv.conf is copied into the chroot
> This should be fixed in the latest unstable upload (not in Testing yet).
> Please check and report if you are still having the problem or close the bug
> if not.
Looks good, thanks.
Bernhard
--- End Message ---
