Question
How to get Postfix to run on 18.04.
- Posted on September 9, 2018
- ApplicationsUbuntu 18.04
Asked by Ian Mitchell
Ubuntu 18.04.1 droplet trying to get Postfix to work. Cannot get past the message active (exited) from the postfix status command. Any ideas would be MUCH APPRECIATED. I have spent days researching and my final brick wall is this Debian bug report:
Message #121 received at 877992@bugs.debian.org (full text, mbox, reply):
From: Scott Kitterman debian@kitterman.com
To: 877992@bugs.debian.org
Subject: Re: Problem still persists in 9.3 – me too
Date: Fri, 23 Feb 2018 18:11:02 -0500
I’ve just uploaded an update that changes how the instance generator works.
It seems to help for some people, but not everyone. It should be in 9.4, so
after Debian 9.4 is out, more reports of this problem, with details, would be
useful.
Scott K
Has anyone found a way to apply this update to 18.04 or a workaround ?? PLEASE Thank you in anticipation, ianm
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Want to learn more? Join the DigitalOcean Community!
Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.
Hey friend!
The “active (exited)” status only means that systemd is not monitoring it, which seems to be more about the default systemd script than anything else. I can confirm on my production postfix boxes (running Ubuntu 18) that they all say the same, but they are all up and running without issue. I might suggest that if postfix is failing for you and you see that status, it indicates a problem with a custom configuration rather than the default state. Perhaps running “postfix check” will reveal an error in the configuration.
Jarland