On 19 Sep 2017, at 22:36, Chris wrote: > On Wed, 2017-09-20 at 04:31 +0200, Reindl Harald wrote: >> >> Am 20.09.2017 um 02:32 schrieb Chris: >>> >>> I then installed dnsmasq (apparently it wasn't installed) >> frankly clean up your mess - you recently posted dnsmasq as well as >> named listening on different interfaces for DNS, now you say dnsmasq >> was >> not installed > > Will do, sorry for all the noise the last few days. I'll see if I can > figure this out myself.
Everyone here started clueless and when we obtained a little knowledge, got dangerous: mostly to ourselves. No apologies needed. You have clearly done something on your system that confuse the specific problem you're having with SpamAssassin. I suspect the root issue is installing dnsmasq from the upstream source distribution (and maybe BIND also?) rather than using the Debian/Ubuntu package(s) via the apt and/or dpkg tools. That's not an uncommon class of mistake, but it is an especially risky move on a systemd-managed platform and especially on anything Debian-based because Debian makes substantial changes to some open source software which can cause unusual problems which are unique to the platform. The bottom line: on Ubuntu, use the Ubuntu software installation tools and do not try to install anything from upstream source that has a Ubuntu package.
signature.asc
Description: OpenPGP digital signature
