On Tue, 7 Aug 2007 at 20:05 -0700, [EMAIL PROTECTED] confabulated:
Thanks for that. Spamd hadn't started. There was an error in the local.cf
file. It looks liek some of the other software I installed modified it.
Thanks for the pointers - it should've been the first place I looked.
Anybody ha
27;m now having
trouble get them to communicate.
Z.
--
View this message in context:
http://www.nabble.com/Unable-to-SPamAssassin-3.2.2-started-tf4233729.html#a12046366
Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
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
> fail
On Tue, 2007-08-07 at 18:01 -0700, 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]:
Are you sure there is spamd process running on the same host calling this?
Looks that there is not.
> 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 se
ug 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.
Zoran
--
View this message in context:
http://www.nabble.com/Unable-to-SPamAssassin-3.2.2-started-tf4233729.html#a12045373
Sent fro
