On 8 Jun 2016, at 9:42, Carlo Manuali wrote:
It works with no changes by using TCP socket (on localhost).
—Carlo
On 8 Jun 2016, at 6:02, Carlo Manuali wrote:
In particular I’ve adopted the local mode, that uses a local socket
(file) in order to establish the communication between them.
[...]
Only when I restart SpamAssassin manually from a shell (with the clamd
started) all goes well. As a matter of fact, I receive on the clamd
logfile the message:
stream(127.0.0.1@1858): OK.
That should have been your strongest clue: "stream(127.0.0.1@1858)" is
clearly describing a connection via TCP on localhost, not a socket node
in the filesystem.
That indicates that clamd was already listening for TCP connections and
that SA at boot time did not try to use TCP or was blocked, while SA
started from a login shell did so successfully. That could be the result
of many different aspects of the environment differences between boot
time and a login shell, including $PATH (if you have more than one SA
and/or Perl installations on different base paths) $HOME (if you are
relying on config files in ~root/.spamassassin) and SELinux file and
runtime contexts (if you have SELinux enabled.)
