Wrong systemd dependencies prevent postfix from starting

[Hadmut Danisch]

Hi,

postfix doesn't start on my machine on boot, while it can be easily started manually after boot.

systemctl status [e-mail]

tells the reason why postfix fails at starttime:

fatal: parameter inet_interfaces: no local interface found for 192.168.200.1

My main.cf contains

inet_interfaces = 127.0.0.1, 192.168.200.1

since my postfix is not intended to be available for the LAN, just for my localhost and the virtual lan for my virtual machines.

At the time systemd tries to start postfix, the virtual lan is not yet configured and thus can't be found by postfix. Which means that systemd dependencies are wrong, postfix should wait for all network devices to be present.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: postfix 3.1.4-4
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CurrentDesktop: XFCE
Date: Wed Apr 19 09:43:58 2017
DuplicateSignature: InvalidHostOrDomain
InstallationDate: Installed on 2016-04-22 (361 days ago)
InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420)
SourcePackage: postfix
UpgradeStatus: Upgraded to zesty on 2017-04-18 (0 days ago)

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1531299, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

[Hadmut Danisch (hadmut)]

I don't see what these bugs have in common, except for a similar error message.

[Hadmut Danisch (hadmut)]

Anyone alive here?

a) This is not a duplicate of #1531299 and a completely different thing.

b) Problem still exists under 17.10.

Anyone willing to solve or is it just intended to not work?

[Scott Kitterman (kitterman)]

I agree it's not a duplicate.

I've seen this in Debian as well and haven't solved it their either.

[Scott Kitterman (kitterman)]

This was fixed in 3.3.2-1.