Sparecreative wrote:
> I've just installed SA 3.2.2 and the installation went fine with no errors.
> Then when I tried to invoke it via a rule in Communigate Pro it fails. I
> checked the logs and this is what I see:
>
> Aug 8 00:22:54 SpareServer spamc[12563]: connect to spamd on 127.0.0.1
> failed, retrying (#1 of 3): Connection refused
> Aug 8 00:22:55 SpareServer spamc[12563]: connect to spamd on 127.0.0.1
> failed, retrying (#2 of 3): Connection refused
> Aug 8 00:22:56 SpareServer spamc[12563]: connect to spamd on 127.0.0.1
> failed, retrying (#3 of 3): Connection refused
> Aug 8 00:22:57 SpareServer spamc[12563]: connection attempt to spamd
> aborted after 3 retries
> Aug 8 00:25:04 SpareServer spamc[12668]: connect to spamd on
> 255.255.255.255 failed, broadcast addr
> Aug 8 00:25:04 SpareServer spamc[12668]: connect to spamd on
> 255.255.255.255 failed, retrying (#1 of 3): Unknown error: 0
> Aug 8 00:25:05 SpareServer spamc[12668]: connect to spamd on
> 255.255.255.255 failed, broadcast addr
> Aug 8 00:25:05 SpareServer spamc[12668]: connect to spamd on
> 255.255.255.255 failed, retrying (#2 of 3): Invalid argument
> Aug 8 00:25:06 SpareServer spamc[12668]: connect to spamd on
> 255.255.255.255 failed, broadcast addr
> Aug 8 00:25:06 SpareServer spamc[12668]: connect to spamd on
> 255.255.255.255 failed, retrying (#3 of 3): Invalid argument
>
>
> Any pointers would really be appreciated.
>
Is spamd actually running? You can't invoke spamc without a spamd to do
the work...
