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 you also remove all the config files?
Yep.
I've got past the problem now, though I can't say I've figured out what was
really wrong with it. With the new version of spamassassin (I assume) the
spamd daemon became disabled, and reenabling it has fixed my problem.
However the original problem can't have been that simple, because I
originally saw no connection refused messages in syslog from spamc, but
instead I saw a report of the spam status of each incoming message. Which
was pretty confusing since it made everything look like it was working
perfectly. Anyway, some combination of purging, reinstalling, and playing
with config files has solved the problem.
The only thing I would say is the unknown error message in SA could be a bit
better, after looking at the code and turning up the debug I could see that
unknown error meant more specifically that no X-Spam-Status header was in
what came back from spamc.
Also, it would be nice if spamc could give some feedback as to the problem
it had, perhaps a header to indicate why it didn't actually do anything with
the message, but that's obviously an issue for the developers of that, not
you.
You are welcome to close this bug, I haven't myself just incase you do want
to use it improve the error messages to aid debugging.
Richard.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
