Re: [exim] Most likely reason for Spam ACL "cannot parse spa…

Top Page
Delete this message
Reply to this message
Author: Ian FREISLICH
Date:  
To: Tom Kistner
CC: Herb Martin, exim-users
Subject: Re: [exim] Most likely reason for Spam ACL "cannot parse spamd output" ?
Tom Kistner wrote:
> Herb Martin wrote:
>
> > What are the most likely reasons for this Spam ACL
> >
> >     "cannot parse spamd output"  ?

>
> That's a blanket error that is thrown whenever the returned output from
> spamd is unparseable (that includes no output at all).
>
> > Environment: Cygwin, Win2003, Exim 3.51
>
> I suppose you mean 4.51, and then there is this "Cygwin" thing, which I
> cannot really support :)
>
> Look in src/spam.c, find that error message and add some debugging code
> around that place that spits out what spamd returns. Then run exim like
> "exim -bd -d" and send mails.


I've mostly seen these when spamd has deid for some reason. IIRC
the return was "0/0" or "0". The most frequent cause was spamd
running out of memory.

Ian

--
Ian Freislich