• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Spamassassin connect to spamd on ::1 failed - doesn't scan messages

LeireL

New Pleskian
Hello,

I have:
Centos 7.2.11
Plesk 12.0.8
postfix-2.10.1-6.el7.x86_64
spamassassin-3.4.0-2.el7.x86_64

I detect some messages aren't scanned by spam, I just receive

<code>
May 16 10:40:36 plesk135 spamc[8789]: connect to spamd on ::1 failed, retrying (#1 of 3): Connection refused
May 16 10:40:36 plesk135 spamd[2005]: spamd: connection from localhost [127.0.0.1]:35592 to port 783, fd 5
May 16 10:40:36 plesk135 spamd[2005]: spamd: using default config for [email protected]: /var/qmail/mailnames/xxxxx.es/yyyyy/.spamassassin/user_prefs
May 16 10:40:36 plesk135 spamd[2005]: spamd: processing message <[email protected]> for [email protected]:30
</code>

Any #2 or #3 rentries.

Antispam setting:
- ON - Switch on server-wide SpamAssassin spam filtering
- ON - Switch on server-wide greylisting spam protection
- On - Apply individual setting to spam filtering

<code>
# cat /etc/sysconfig/spamassassin
# Options to spamd
SPAMDOPTIONS="--nouser-config --username=popuser --daemonize --helper-home-dir=/var/qmail --virtual-config-dir=/var/qmail/mailnames/%d/%l/.spamassassin --create-prefs --max-children=5"
<code>
 
Looks like the problem is related to IPv6 address. Try to disable it with adding option --ipv4-only to /etc/sysconfig/spamassassin
Restart spamassassin after that with

# /etc/init.d/spamassassin stop
# /etc/init.d/spamassassin start

# cat /etc/sysconfig/spamassassin
# Options to spamd
SPAMDOPTIONS="--nouser-config --ipv4-only --username=popuser --daemonize --helper-home-dir=/var/qmail --virtual-config-dir=/var/qmail/mailnames/%d/%l/.spamassassin --create-prefs --max-children=1"
 
Maybe --ipv4-only is incorrect option?

root 7878 0.5 2.9 276664 61696 ? Ss 12:47 0:01 /usr/bin/spamd --pidfile /var/run/spamd.pid --ipv4-only --nouser-config --username=popuser --daemonize --helper-home-dir=/var/qmail --virtual-config-dir=/var/qmail/mailnames/%d/%l/.spamassassin --create-prefs --max-children=5

The issue continues

May 16 12:50:33 plesk135 spamc[8584]: connect to spamd on ::1 failed, retrying (#1 of 3): Connection refused
May 16 12:50:39 plesk135 spamc[8612]: connect to spamd on ::1 failed, retrying (#1 of 3): Connection refused
 
Or completely disable IPv6 on server level if you do not use it.
 
I don't use IPv6, but I have more servers with the same configuration and SpamAssassin works fine; without ipv4 option, just default options.

Any more ideas to solve it?
 
I know this is old, but perhaps the best thing is to REMOVE the --ipv4-only option.. let spamd listen to both ipv4 and ipv6 addresses..
 
Back
Top