[Bug 1519331] Re: Postfix cannot resolve DNS if network was unavailable when it was started, such as on a laptop

It's postfix@$INSTANCE. If you don't have multi-instance setup, the default instance is "-", so you would look for postfix@-, not postfix@. This is discussed in README.Debian. You should probably file a new bug for this problem if you don't get it figured out. -- You received this bug

[Bug 1519331] Re: Postfix cannot resolve DNS if network was unavailable when it was started, such as on a laptop

This bug is back in Ubuntu 20.04 postfix/focal-updates,now 3.4.13-0ubuntu1.2 I'm not certain of my analysis, but I see two services postfix.service - [Unit] Description=Postfix Mail Transport Agent Conflicts=sendmail.service exim4.service

[Bug 1519331] Re: Postfix cannot resolve DNS if network was unavailable when it was started, such as on a laptop

This bug was fixed in the package postfix - 3.1.4-4ubuntu1 --- postfix (3.1.4-4ubuntu1) zesty; urgency=medium * Use correct service dependencies in postfix@.service, to avoid racing systemd-resolved at boot. LP: #1519331. -- Steve Langasek Sat,

[Bug 1519331] Re: Postfix cannot resolve DNS if network was unavailable when it was started, such as on a laptop

The reason for it not being released for zesty before was that it seemed to have 3 undefined autopkgtest failures for sbuild. After looking into those now, it seems that the sbuild autopkgtests seem to be constantly failing for those 3 archs for all packages - so, (most likely) unrelated to the

[Bug 1519331] Re: Postfix cannot resolve DNS if network was unavailable when it was started, such as on a laptop

Anything in particular holding the release of this fix for Zesty? -- 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

[Bug 1519331] Re: Postfix cannot resolve DNS if network was unavailable when it was started, such as on a laptop

This bug was fixed in the package postfix - 3.1.0-5ubuntu1 --- postfix (3.1.0-5ubuntu1) yakkety; urgency=medium * Use correct service dependencies in postfix@.service, to avoid racing systemd-resolved at boot. LP: #1519331. -- Steve Langasek Sat,

[Bug 1519331] Re: Postfix cannot resolve DNS if network was unavailable when it was started, such as on a laptop

Test case confirmed also on yakkety. ** Tags removed: verification-needed-yakkety ** Tags added: verification-done-yakkety ** Tags removed: verification-needed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1519331] Re: Postfix cannot resolve DNS if network was unavailable when it was started, such as on a laptop

Ran through the full test case on zesty and confirmed that this works as expected. ** Tags removed: verification-needed-zesty ** Tags added: verification-done-zesty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1519331] Re: Postfix cannot resolve DNS if network was unavailable when it was started, such as on a laptop

I've installed the proposed the package (on zesty), removed my workaround in /etc/rc.local, rebooted and it seems to work. Thanks! -- 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:

[Bug 1519331] Re: Postfix cannot resolve DNS if network was unavailable when it was started, such as on a laptop

Proposed package installed on zesty, workaround removed (/etc/systemd/system/postfix@-.service.d/override.conf) and rebooted. So far so good :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1519331

[Bug 1519331] Re: Postfix cannot resolve DNS if network was unavailable when it was started, such as on a laptop

Hello Erik, or anyone else affected, Accepted postfix into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/postfix/3.1.4-4ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See

[Bug 1519331] Re: Postfix cannot resolve DNS if network was unavailable when it was started, such as on a laptop

** Changed in: postfix (Ubuntu Yakkety) Status: Triaged => In Progress ** Changed in: postfix (Ubuntu Zesty) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1519331] Re: Postfix cannot resolve DNS if network was unavailable when it was started, such as on a laptop

** Description changed: - Every now and then postfix installed on my laptop stops delivering - mails. 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. + [SRU Justification] + Race

[Bug 1519331] Re: Postfix cannot resolve DNS if network was unavailable when it was started, such as on a laptop

** Changed in: postfix (Debian) Status: Unknown => Fix Released -- 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

[Bug 1519331] Re: Postfix cannot resolve DNS if network was unavailable when it was started, such as on a laptop

Marking this high; racing /etc/resolv.conf setup at boot is not just a desktop issue. ** Changed in: postfix (Ubuntu) Status: Confirmed => Fix Released ** Bug watch added: Debian Bug tracker #854475 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854475 ** Also affects: postfix

[Bug 1519331] Re: Postfix cannot resolve DNS if network was unavailable when it was started, such as on a laptop

Adding the local recursive name server to /etc/resolvconf/resolv.conf.d/base (see comment #34) solved the problem of having an unusable /etc/resolv.conf at the time postfix copies it during boot. Together with restarting postfix whenever /etc/resov.conf changes solves my problems. I would be

[Bug 1519331] Re: Postfix cannot resolve DNS if network was unavailable when it was started, such as on a laptop

I have just added something to the file /etc/resolvconf/resolv.conf.d/base to try to have a useful /etc/resolv.conf all the time: ``` # workaround for broken interactions with Postfix: # fall back to the local name server 127.0.1.1 nameserver 127.0.1.1 ``` Let's see how this plays out...

[Bug 1519331] Re: Postfix cannot resolve DNS if network was unavailable when it was started, such as on a laptop

Hi, I see two problems to solve to enable using Postfix on laptops with changing network connectivity: 1. Copy a working /etc/resolve.conf on initial Postfix start-up 2. Adjust Postfix's copy of /etc/resolv.conf in /var/spool/postfix/etc/resolv.conf Part 1 seems to be tackled with waiting for

Re: [Bug 1519331] Re: Postfix cannot resolve DNS if network was unavailable when it was started, such as on a laptop

On Mon, May 15, 2017 at 09:59:22PM -0700, Steve Langasek wrote: > > - The penalty of pulling in network-online.target is simply that for the > > local case postfix is started a bit later then necessary during boot. > There's no reason that this *should* be true for an intermittently-online >

Re: [Bug 1519331] Re: Postfix cannot resolve DNS if network was unavailable when it was started, such as on a laptop

Hi Scott, Adding the Debian bug on Cc:. On Mon, May 15, 2017 at 10:12:41PM -, Scott Kitterman wrote: > On Monday, May 15, 2017 08:49:42 PM you wrote: > > On Mon, May 15, 2017 at 06:45:21PM -, Scott Kitterman wrote: > > > I'm getting close to uploading a fix for this to Debian, so you

Re: [Bug 1519331] Re: Postfix cannot resolve DNS if network was unavailable when it was started, such as on a laptop

On Monday, May 15, 2017 08:49:42 PM you wrote: > On Mon, May 15, 2017 at 06:45:21PM -, Scott Kitterman wrote: > > I'm getting close to uploading a fix for this to Debian, so you might wait > > for that. > > It looks like you've implemented this using the network-online.target > approach,

Re: [Bug 1519331] Re: Postfix cannot resolve DNS if network was unavailable when it was started, such as on a laptop

On Mon, May 15, 2017 at 06:45:21PM -, Scott Kitterman wrote: > I'm getting close to uploading a fix for this to Debian, so you might wait > for that. It looks like you've implemented this using the network-online.target approach, which as you mentioned might not DTRT for the localhost-only

Re: [Bug 1519331] Re: Postfix cannot resolve DNS if network was unavailable when it was started, such as on a laptop

I'm getting close to uploading a fix for this to Debian, so you might wait for that. -- 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

[Bug 1519331] Re: Postfix cannot resolve DNS if network was unavailable when it was started, such as on a laptop

I am seeing this issue on Ubuntu 17.04. /var/spool/postfix/etc/resolv.conf is pointing at 192.168.122.1, which is the IP of my libvirt bridge - this is a result of dnsmasq interfacing with resolvconf, so that the host system can resolve local hostnames of guests on the bridge. It's fine that

[Bug 1519331] Re: Postfix cannot resolve DNS if network was unavailable when it was started, such as on a laptop

Same issue here on zesty, empty /var/spool/postfix/etc/resolv.conf after reboot. Applying solution from #24 works it around: ``` # printf "[Unit]\nAfter=network-online.target\n" | sudo SYSTEMD_EDITOR=tee systemctl edit postfix@-.service ``` Current working configuration: ``` # systemctl cat

[Bug 1519331] Re: Postfix cannot resolve DNS if network was unavailable when it was started, such as on a laptop

Another confirmation that this bug is still present in Zesty, and that the solution in #24 has worked fine for me so far. -- 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

[Bug 1519331] Re: Postfix cannot resolve DNS if network was unavailable when it was started, such as on a laptop

Had the same problem before Zesty and used some of the fixes described here to have postfix restart through rc.local file after waiting a few minutes. The bug is still persistent for me after upgrading to Zesty. What does fix it for me though is adding the "After" line to the Unit:

[Bug 1519331] Re: Postfix cannot resolve DNS if network was unavailable when it was started, such as on a laptop

I experience this on Zesty, on an always-on machine, that however relies on DHCP for network configuration. I would argue that this is an upstream bug, or if you want a design flaw. It is perfectly normal for resolv.conf to change at arbitrary moments. Examples are VPN and alternative redundant

[Bug 1519331] Re: Postfix cannot resolve DNS if network was unavailable when it was started, such as on a laptop

Can confirm that this bug exists on Zesty. It occurs on my desktop machine which has network available at boot time via cabled ethernet. -- 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:

[Bug 1519331] Re: Postfix cannot resolve DNS if network was unavailable when it was started, such as on a laptop

I am using the following script saved as /etc/resolvconf/update.d/postfix: ``` #! /bin/sh # restart Postfix whenever resolv.conf changes, because Postfix creates # a local copy of the file for use from inside its chroot /usr/sbin/service postfix restart ``` That works reliably when changing

[Bug 1519331] Re: Postfix cannot resolve DNS if network was unavailable when it was started, such as on a laptop

As I see it, the only reliable methods found to date are described in message #7 (https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1519331/comments/7), message #17 (https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1519331/comments/17), and message #19

[Bug 1519331] Re: Postfix cannot resolve DNS if network was unavailable when it was started, such as on a laptop

The only workaround I could get to work was to restart postifx on network up by adding `/etc/network/if-up.d/999local` with the following contents: ``` #!/bin/sh -e # Called when a new interface comes up # Local workarounds # Fix postfix boot up issue: #

[Bug 1519331] Re: Postfix cannot resolve DNS if network was unavailable when it was started, such as on a laptop

FWIW, I tried a bunch of different combinations of After, BindsTo, PartOf, and ReloadPropagatedFrom in /lib/systemd/system/postfix.service and none of them addressed the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1519331] Re: Postfix cannot resolve DNS if network was unavailable when it was started, such as on a laptop

In case it helps other people, here is the workaround I use, in /etc/rc.local: = while ! grep -q nameserver /etc/resolv.conf do sleep 30 done cp /etc/resolv.conf /var/spool/postfix/etc/resolv.conf /etc/init.d/postfix restart = -- You

[Bug 1519331] Re: Postfix cannot resolve DNS if network was unavailable when it was started, such as on a laptop

Just tried this with Zesty and Postfix 3.1.4-4. I have ipv4 dhcp, ipv6 static and resolv.conf. After reboot /var/spool/postfix/etc/resolv.conf did not have any addresses in it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

Re: [Bug 1519331] Re: Postfix cannot resolve DNS if network was unavailable when it was started, such as on a laptop

On Monday, January 30, 2017 09:33:36 PM you wrote: > Which package was updated to fix this problem in Zesty? I could try to > upgrade it only (I'm not ready to upgrade the whole distro). postfix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed

[Bug 1519331] Re: Postfix cannot resolve DNS if network was unavailable when it was started, such as on a laptop

Which package was updated to fix this problem in Zesty? I could try to upgrade it only (I'm not ready to upgrade the whole distro). -- 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:

[Bug 1519331] Re: Postfix cannot resolve DNS if network was unavailable when it was started, such as on a laptop

It would be nice if someone who is having this problem could test 3.1.4-2 or later on Zesty to see if the problem is fixed (I think it is). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1519331

[Bug 1519331] Re: Postfix cannot resolve DNS if network was unavailable when it was started, such as on a laptop

>@Marius Gedminas (mgedmin) >Curiously, I never saw this problem on my laptop in Ubuntu versions >up to and including 16.04 LTS. >I'm seeing a lot of this problem ever since I upgraded to 16.10 LTS. I experienced the same issues when deploying Ubuntu 16.10 to a new MiniPC (opposed to Ubuntu

Re: [Bug 1519331] Re: Postfix cannot resolve DNS if network was unavailable when it was started, such as on a laptop

On Monday, December 19, 2016 08:58:24 AM you wrote: > > This is about how we integrate postfix and networking in Debian (and > > thus Ubuntu). It's not an upstream issue. Removing the needs-upstream- > report tag. > > By "upstream", I meant Debian. I'm not aware of a separate bug tag for > that.

[Bug 1519331] Re: Postfix cannot resolve DNS if network was unavailable when it was started, such as on a laptop

> This is about how we integrate postfix and networking in Debian (and thus Ubuntu). It's not an upstream issue. Removing the needs-upstream- report tag. By "upstream", I meant Debian. I'm not aware of a separate bug tag for that. What should I be using instead of needs-upstream-report when it

[Bug 1519331] Re: Postfix cannot resolve DNS if network was unavailable when it was started, such as on a laptop

I like the solution proposed in message #7. :-) -- 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

[Bug 1519331] Re: Postfix cannot resolve DNS if network was unavailable when it was started, such as on a laptop

This is about how we integrate postfix and networking in Debian (and thus Ubuntu). It's not an upstream issue. Removing the needs-upstream- report tag. ** Tags removed: needs-upstream-report -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 1519331] Re: Postfix cannot resolve DNS if network was unavailable when it was started, such as on a laptop

** Tags added: needs-upstream-report -- 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

[Bug 1519331] Re: Postfix cannot resolve DNS if network was unavailable when it was started, such as on a laptop

In the postfix service file (/lib/systemd/system/postfix.service), if you change: After=network.target to: Requires=network-online.target After=network-online.target does that solve your problem? Note: this is not a general solution as it breaks setups that only interface with localhost. --

[Bug 1519331] Re: Postfix cannot resolve DNS if network was unavailable when it was started, such as on a laptop

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

[Bug 1519331] Re: Postfix cannot resolve DNS if network was unavailable when it was started, such as on a laptop

Curiously, I never saw this problem on my laptop in Ubuntu versions up to and including 16.04 LTS. I'm seeing a lot of this problem ever since I upgraded to 16.10 LTS. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1519331] Re: Postfix cannot resolve DNS if network was unavailable when it was started, such as on a laptop

Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: postfix (Ubuntu) Status: New => Confirmed -- 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:

[Bug 1519331] Re: Postfix cannot resolve DNS if network was unavailable when it was started, such as on a laptop

Thank you for taking the time to report this bug and helping to make Ubuntu better. Importance -> Low since this doesn't affect the primary use of Postfix as a server MTA, but only with network-manager on a desktop machine. FWIW, I use msmtp. I can't queue mails when offline, but otherwise it

[Bug 1519331] Re: Postfix cannot resolve DNS if network was unavailable when it was started, such as on a laptop

Thank you for taking the time to report this bug and helping to make Ubuntu better. Importance -> Low since this doesn't affect the primary use of Postfix as a server MTA, but only with network-manager on a desktop machine. FWIW, I use msmtp. I can't queue mails when offline, but otherwise it