One thing I have just noticed, On the server which is not working the dspam.debug log file finishes at this point each time:
22754: [09/03/2007 11:57:32] message result: NOT SPAM However on the secondary server which is currently working there are two additional lines after this: 4709: [09/03/2007 12:08:44] delivering message 14709: [09/03/2007 12:08:44] DSPAM Instance Shutdown. Exit Code: 0 I would assume this means something is wrong with delivery on the broken box, I'm still investigating... Cheers On Mon, 2007-09-03 at 10:40 +1200, Paul England wrote: > Hi there, > > I'm currently administrating an email system which uses dspam for spam > filtering, unfortunately I did not initially configure this so I am > still getting my head around how everything works. > > We now have a problem where dspam appears to scan one email and then > stop completely... > > In /var/log/mail.err I get this thousands of times: > > Sep 3 10:31:57 titania dspam[18810]: Connection to > socket /tmp/dspam.sock failed: Connection refused > Sep 3 10:31:57 titania dspam[18810]: Client exited with error -5 > > I've looked at as many logs as possible looking for an explanation > however I can't find much... > > I am running Debian 3.1 Kernel 2.6.14.3, dspam 3.6.8-4, postfix 2.3.3-1 > > I have turned on debug mode in /etc/dspam/dspam.conf using: > > Debug * > DebugOpt process classify spam fp inoculation corpus > > An example of the output is available on pastebin, here is a link: > > http://pastebin.ca/679353 > > If I tail this debug log and restart dspam, I can see that it scans one > email and then mail.err starts giving the 'Connection Refused' error. > > This is where I'm up to... my next stop is to start trying to debug > dspampd... > > Any help would be greatly appreciated, > > Cheers, > > Paul England, > Auckland, New Zealand.
