On Tue, Sep 25, 2007 at 03:30:21PM +1000, Alex Samad wrote: > On Mon, Sep 24, 2007 at 04:03:47PM -0700, Andrew Sackville-West wrote: > > On Sun, Sep 23, 2007 at 06:40:58PM -0400, Daniel D Jones wrote: > > > On Monday 24 September 2007 15:50:58 Andrew Sackville-West wrote: > > > > On Sun, Sep 23, 2007 at 03:36:45PM -0400, Daniel D Jones wrote: > > > > > > > SA should log to /var/log/mail.info, and that's a good place to look > > > > for info... > > > > > > I have two spamd entries in mail.info: > > > > > > Sep 24 14:51:09 etch spamd[10151]: spamd: connection from localhost > > > [127.0.0.1] at port 43270 > > > Sep 24 14:51:11 etch spamd[10151]: spamd: bad protocol: header error: > > > at /usr/sbin/spamd line 1671, <GEN4> line 1. > > > Sep 24 14:51:12 etch spamd[10150]: prefork: child states: II > > > > > > and > > > > > > Sep 24 15:26:20 etch spamd[10151]: spamd: connection from localhost > > > [127.0.0.1] at port 60337 > > > Sep 24 15:26:26 etch spamd[10151]: spamd: bad protocol: header error: > > > ÿôÿý_ > > > at /usr/sbin/spamd line 1671, <GEN5> line 1. > > > Sep 24 15:26:26 etch spamd[10150]: prefork: child states: II > > > > > > If I'm interpreting this correctly, this was a couple of malformed > > > messages > > > which caused spamd to choke. Apparently, then, spamd is being called and > > > passed the messages for examination. > > > > huh. I get copious output from spamd with every mail that hits it. How > > are you starting spamd? > > > > ps aux | grep spamd | grep -v grep > I might not be able to add much to the exim discussion but you can do > > ps aux | grep [s]pamd
huh. good one, thanks! A
signature.asc
Description: Digital signature
