I sent this once already and it never made it onto the bug tracker, so
trying again.
Which means SA-Exim did work, but SpamAssassin itself failed for some
reason. It would be great if you can search through your logs and see if
you can find out why SpamAssassin isn't working.
From syslog:
May 14 14:29:41 localhost spamd[14765]: spamd: connection from localhost
[127.0.0.1] at port 34030
May 14 14:29:41 localhost spamd[14765]: spamd: setuid to Debian-exim
succeeded
May 14 14:29:41 localhost spamd[14765]: spamd: processing message
<[EMAIL PROTECTED]> for Debian-exim:102
May 14 14:29:41 localhost spamd[14765]: spamd: clean message (1.9/5.0) for
Debian-exim:102 in 0.6 seconds, 994 bytes.
May 14 14:29:41 localhost spamd[14765]: spamd: result: . 1 -
AWL,DNS_FROM_RFC_ABUSE,DNS_FROM_RFC_POST,MSGID_FROM_MTA_HEADER
scantime=0.6,size=994,user=Debian-exim,uid=102,required_score=5.0,rhost=localhost,raddr=127.0.0.1,rport=34030,mid=<[EMAIL PROTECTED]>,autolearn=no
May 14 14:29:41 localhost spamd[14764]: prefork: child states: II
Looks to me like SA is happy at it's end. Please let me know what else to
collect/try.
Richard.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
