From: Sander Smeenk <[EMAIL PROTECTED]>
I don't really know what might cause this all. Did you change something
in your spamassassin/local.cf? Or maybe made changes to sa-exim.conf?
Nothing in the spamassassin file was changed, and no recent changes to
sa-exim conf.
Or with purging, did yo
Quoting Richard Burton ([EMAIL PROTECTED]):
> I'm drowning in spam here, any more ideas on what I can check? I've tried
> purging the sa-exim and spam assassin packages and reinstalling, didn't
> help. Logs still show SA appears to be working fine, but sa-exim is still
> saying there was an unk
I'm drowning in spam here, any more ideas on what I can check? I've tried
purging the sa-exim and spam assassin packages and reinstalling, didn't
help. Logs still show SA appears to be working fine, but sa-exim is still
saying there was an unknown failure.
Richard.
--
To UNSUBSCRIBE, ema
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:
Quoting Richard Antony Burton ([EMAIL PROTECTED]):
> Log contains:
> 2006-05-13 13:39:42 1FetPI-0005GT-MT SA: Action: SA didn't successfully run
> against message
Which means SA-Exim did work, but SpamAssassin itself failed for some
reason. It would be great if you can search through your logs a
Package: sa-exim
Version: 4.2.1-2
Severity: grave
Justification: renders package unusable
Since updating spamassassin package to 3.1.1 sa-exim no longer has incoming mail
scanned.
Log contains:
2006-05-13 13:39:42 1FetPI-0005GT-MT SA: Action: SA didn't successfully run agai
nst message, accepting
6 matches
Mail list logo
