First I run /etc/init.d/nullmailer start and it tells me that it cannot start, and I have to run emerge --config nullmailer first. I do so, then re-run /etc/init.d/nullmailer start, and I get the same exact message. I believe emerge --config nullmailer should report problems it encounters before exiting, and even exit with a non-zero status, so that I can more easily diagnose and fix the issue. Attached the console output.
Created attachment 550044 [details] user experience
does this apply to all versions in the tree?
To set the defaultdomain, 'emerge --config nullmailer' uses this command: $ hostname --domain Do you have some domain name set?
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=24c1f8418e70e3c9050942653e385da982ab2ced commit 24c1f8418e70e3c9050942653e385da982ab2ced Author: Michael Haubenwallner <haubi@gentoo.org> AuthorDate: 2019-02-26 16:37:46 +0000 Commit: Michael Haubenwallner <haubi@gentoo.org> CommitDate: 2019-04-01 08:14:04 +0000 mail-mta/nullmailer: revbump and more Revbump, EAPI 7, add myself as maintainer. Closes: https://bugs.gentoo.org/654124 Add ~arm keyword. Closes: https://bugs.gentoo.org/664514 Fix permission for /var/spool/nullmailer/failed, credits to John R. Graham. Closes: https://bugs.gentoo.org/622738 Keep dir /var/spool/nullmailer/failed. Closes: https://bugs.gentoo.org/651288 No not depend on sys-apps/groff. Closes: https://bugs.gentoo.org/604316 Tell if 'emerge --config' gets empty FQDN or domainname, and remind to tweak /etc/nullmailer/remotes. Closes: https://bugs.gentoo.org/668104 Block with USE=mta against msmtp,opensmtpd,ssmtp. Closes: https://bugs.gentoo.org/631654 Package-Manager: Portage-2.3.51, Repoman-2.3.11 Signed-off-by: Michael Haubenwallner <haubi@gentoo.org> mail-mta/nullmailer/Manifest | 1 + mail-mta/nullmailer/metadata.xml | 4 + mail-mta/nullmailer/nullmailer-2.2.ebuild | 148 ++++++++++++++++++++++++++++++ 3 files changed, 153 insertions(+)
