Steve: Maybe my comment does not really belong here, I agree. I admit
that I have not fully investigated the problem -- the problem in my case
being that a configuration with static IP does not appear to set the DNS
correctly, either via netplan (and networkd) or via systemd's resolver.
A web searc
There seem to be a number of workarounds on the Web, and most of them
revolve around modifying either the netplan config file or the systemd
resolver config. None really worked for me -- usually, the resolver
configuration did not survive a reboot.
I found a very unclean (but effective) workaround
I observed the same behavior in a new Ubuntu-Server 18.04 install.
It is possible that this behavior is related to two instances of
Spamassassin running. Disabling the standalone Spamassassin ("systemctl
disable spamassassin.service") made this problem go away. I still can
see the spam check in th
