https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6939
Bug ID: 6939
Summary: spamc[7611]: connect(AF_UNIX) to spamd failed:
Connection refused
Product: Spamassassin
Version: 3.3.2
Hardware: PC
OS: Linux
Status: NEW
Severity: blocker
Priority: P2
Component: spamc/spamd
Assignee: [email protected]
Reporter: [email protected]
For each attempt to scan an email for junk via spamassassin / Evolution 3.6.4,
the following is noted in /var/log/mail.err:
spamc[7611]: connect(AF_UNIX) to spamd failed: Connection refused
My SpamAssassin appears to be configured correctly from what I can see as well:
$ cat /etc/default/spamassassin
# /etc/default/spamassassin
# Duncan Findlay
# WARNING: please read README.spamd before using.
# There may be security risks.
# Change to one to enable spamd
ENABLED=1
# Options
# See man spamd for possible options. The -d option is automatically added.
# SpamAssassin uses a preforking model, so be careful! You need to
# make sure --max-children is not set to anything higher than 5,
# unless you know what you're doing.
OPTIONS="--create-prefs --max-children 5 --helper-home-dir"
# Pid file
# Where should spamd write its PID to file? If you use the -u or
# --username option above, this needs to be writable by that user.
# Otherwise, the init script will not be able to shut spamd down.
PIDFILE="/var/run/spamd.pid"
# Set nice level of spamd
#NICE="--nicelevel 15"
# Cronjob
# Set to anything but 0 to enable the cron job to automatically update
# spamassassin's rules on a nightly basis
CRON=1
The process appears to be running as well:
$ ps aux | grep spam
kip 2789 0.0 0.8 131616 32988 ? S May09 0:09 /usr/bin/perl
-T -w /usr/sbin/spamd --socketpath /run/user/kip/spamd-socket-path-2WUQWW
--max-children=1 --pidfile /run/user/kip/spamd-pid-file-JWUQWW
kip 2805 0.0 1.3 141548 52784 ? S May09 0:08 spamd child
root 18498 0.0 1.4 155436 57264 ? Ss 13:47 0:01
/usr/sbin/spamd --create-prefs --max-children 5 --helper-home-dir -d
--pidfile=/var/run/spamd.pid
root 18551 0.0 1.4 159100 60480 ? S 13:48 0:00 spamd child
root 18552 0.0 1.3 155436 54692 ? S 13:48 0:00 spamd child
kip 23006 0.0 0.0 16632 944 pts/10 S+ 14:28 0:00 grep
--color=auto spam
This was working fine in Ubuntu 12.04, but stopped working upon a fresh install
to 13.04.
--
You are receiving this mail because:
You are the assignee for the bug.
