Yup, either fix spamd so it listens on localhost (you'd see a LISTEN on port 783, which is missing), or correct your spamc flags to include -U /var/spool/postfix/spamass/spamd.sock
-Dan > On Sep 28, 2021, at 11:45 AM, Viktor Dukhovni <postfix-us...@dukhovni.org> > wrote: > > On Tue, Sep 28, 2021 at 08:38:33PM +0200, Maurizio Caloro wrote: > >> Sep 28 15:11:22 nmail spamd[3826]: prefork: child states: II > > The "spamd" server appears to be running... > >> Sep 28 15:11:23 nmail spamc[4525]: connect to spamd on 127.0.0.1 failed, >> retrying (#1 of 3): Connection refused >> Sep 28 15:11:24 nmail spamc[4525]: connection attempt to spamd aborted after >> 3 retries > > The "spamc" client is unable to connect via "127.0.0.1" (via some port). > >> /etc/default/spamsassassin >> >> OPTIONS="--nouser-config --create-prefs --max-children 5 --helper-home-dir >> /var/lib/spamassassin --username=debian-spamd --groupname=debian-spamd >> --siteconfigpath /etc/spamassassin >> -socketpath=/var/spool/postfix/spamass/spamd.sock--socketowner=debian-spamd >> --socketgroup=debian-spamd --socketmode=0660" > > The server is is configured to listen on a unix-domain socket at: > > -socketpath=/var/spool/postfix/spamass/spamd.sock > > so perhaps not listening on 127.0.0.1 is not surprising. > > -- > Viktor.
