Hi,
Just recently upgraded (16.04 LTS => 17.04), and I can confirm this bug
and workaround / fix as well. It definitely exists in 17.04.
Is the fix "OK"? Meaning what does it potentially break?
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I fixed this problem. In my case it had to do with booting from a SSD,
and not all services had completed their startup when postfix was
started. Please see:
https://askubuntu.com/questions/929407/postfix-problem-when-started-
from-ssd/931070?noredirect=1#comment1505997_931070
It looks like I
I can also reproduce this problem on a clean Kubuntu 17.04 installation
I did yesterday.
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 17.04
Release:17.04
Codename: zesty
$ sudo apt list postfix:
Auflistung... Fertig
I'm seeing the same issue on 17.04 with postfix. The patch described
here is implemented in postfix-3.1.4-4, but I still have to update the
resolve.conf in the postfix chroot every time I reboot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
To clarify my testbed, I can reliably reproduce this issue by rebooting
a laptop with Ubuntu Desktop 16.10 installed. Neither restarting the
network-manager service, nor reconnecting to the same network using the
nm-applet reproduce the issue, but rebooting does.
--
You received this bug
I manually applied the 2 commits in
https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1627117/comments/5
but the problem still occurs, so I doubt the new release is a fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug was fixed in the package postfix - 3.1.3-2
---
postfix (3.1.3-2) unstable; urgency=medium
[Scott Kitterman]
* Use main/master.cf from /usr/share/postfix/ for multi-instance prototypes
rather than from /etc/postfix as, depending on configuration, they may not
** Tags added: patch server-next
--
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
This is fixed in Debian and Ubuntu Zakkety. Someone involved in Ubuntu
development will need to do an SRU to fix the earlier releases. You
need these two commits:
https://git.launchpad.net/postfix/commit/?h=stable/v3.1=6a19708c5e0dfd188df8898028a9977b811230f5
I'm facing this bug after upgrading from xenial to yakkety.
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.10
Release:16.10
Codename: yakkety
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: postfix (Ubuntu)
Status: Triaged => Fix Committed
--
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
Yes, what you did with lxc seems to be reproducing the same issue I am
seeing.
I am running Yakkety, but I actually did try backporting the package to
Xenial and saw the same issue there too.
The script that copies the /etc/resolv.conf (and other files) into the
chroot is
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
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/1627117
Title:
** Changed in: postfix (Ubuntu)
Status: Confirmed => Triaged
** Changed in: postfix (Ubuntu)
Importance: Undecided => Medium
--
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:
15 matches
Mail list logo
