And I note I didn't do a very good job of adding those X's. Oh well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649453
Title:
systemd starts postfix before resolver
To manage notifications abou
Sorry to jump on this six-month-old bug, but it seems to be describing
exactly what's still going wrong for me. When I reboot my system running
Postfix, no mail is sent, and I get the following output when I run
"mailq":
-Queue ID- --Size-- Arrival Time -Sender/Recipient---
47F291B6B
This bug was fixed in the package postfix - 3.1.4-2
---
postfix (3.1.4-2) unstable; urgency=medium
* Update postfix Suggestions.
* Update postfix-sqlite postinst/prerm to reflect that addmap is idempotent.
* Restore so.1.0.1 symlinks for map libraries and change how new entries
Now that the upload I had pending is done, I did look into this a bit
further.
By adding the After=network-online.target override, when I look at the
output of systemd-analyze critical-chain with and without an equivalent
Wants= postfix is starting after network-online.target.
I didn't look expli
On Wednesday, January 04, 2017 07:28:27 AM you wrote:
> Thanks. OOI, does it really hurt to have the After=systemd-
> resolved.service even for cases where it's not strictly needed?
Probably not. We've got a huge stack of changes queued, of which this is a
small part. I'll look at this for the
Thanks. OOI, does it really hurt to have the After=systemd-
resolved.service even for cases where it's not strictly needed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649453
Title:
systemd start
On Tuesday, January 03, 2017 08:43:15 PM you wrote:
> @Scott:
> https://git.launchpad.net/postfix/commit/?h=stable/v3.1&id=1a190cf17cc02
> looks rather complicated and also creates an unmanaged config file. Why
> not just always add those After= to the .service? If resolved is not
> enabled, then A
@Scott:
https://git.launchpad.net/postfix/commit/?h=stable/v3.1&id=1a190cf17cc02
looks rather complicated and also creates an unmanaged config file. Why
not just always add those After= to the .service? If resolved is not
enabled, then After=systemd-resolved is a no-op (it's only ordering, not
a de
OK. Thanks for the update.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649453
Title:
systemd starts postfix before resolver
To manage notifications about this bug go to:
https://bugs.launchpad.n
On Tuesday, January 03, 2017 12:34:12 AM you wrote:
> Any idea when the fix will appear in updates for yakkety?
We plan on an upload to Debian in the next day or two. It'll follow into
Ubuntu shortly there after. A Yakkety SRU is work for someone involved in
Ubuntu to do, so no.
--
You recei
Any idea when the fix will appear in updates for yakkety?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649453
Title:
systemd starts postfix before resolver
To manage notifications about this bug
** 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/1649453
Title:
systemd starts postfix before resolver
To manage notifications a
** Changed in: postfix (Ubuntu)
Importance: Undecided => High
** Changed in: postfix (Ubuntu)
Assignee: (unassigned) => Scott Kitterman (kitterman)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
On Tuesday, December 20, 2016 12:21:51 AM you wrote:
> This is probably also an issue on Debian, would you be willing to file a
> bug there? Against postfix specifically.
There's no need. I'm already looking at it.
Scott K
--
You received this bug notification because you are a member of Ubunt
This is probably also an issue on Debian, would you be willing to file a
bug there? Against postfix specifically.
** Changed in: postfix (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
** Also affects: postfix (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649453
Title:
systemd starts postfix before resolver
To manage notificat
16 matches
Mail list logo
