On 6/7/20 10:31 AM, R. G. Newbury wrote:
It was apparently something to do with selinux. I usually disable
selinux as the first or second thing I do to a new install. I forgot to
do that.
That should never be necessary.
A quick edit to /etc/selinux/config and a reboot solved removed the
annoyance. (I cannot say 'solved the problem as I have no idea what the
actual problem was: this was the 'sledge-hammer for walnuts' resolution.)
Now how you deciphered that that was where the error came from is just
further evidence that far too much of system management is arcane magic:
Clarke's Law: Any sufficiently advanced technology is
indistinguishable from magic.
Oddly 1) I was running as root... so *who/what* was the 'unauthorized
sender'? and
That sounds like a likely cause right there. Why are you doing that?