Well, some progress
1) The problem with spamd was that, running as vscan it couldn't read
/etc/mail/spamassassin. My own dumb fault, corrected this and the log
now looks a lot healthier.
2) Amavisd-new seems to call perl-spamassassing directly, and keeps
child processes running at the ready. So s
Jack,
Thanks for the suggestion, I may indeed do that, but at the moment
spamd isn't generating any messages after its startup. (unless I telnet
to it)
I start spamd with a script that came with the rpm package from SuSE in
/etc/init.d, the options are specified in the file /etc/sysconfig/spamd,
At 09:51 AM 12.7.2004 -0500, Info wrote:
>Theo,
>
>Thanks for the reply, and there may be some truth in that, but I'm not
>convinced that it is ever working correctly.
>
>There have been NO spamd debug messages in the log since then, despite
>emails being scanned.
>
>There is never any message say
Theo,
Thanks for the reply, and there may be some truth in that, but I'm not
convinced that it is ever working correctly.
There have been NO spamd debug messages in the log since then, despite
emails being scanned.
There is never any message saying it actually found the Bayes data. I am
not con
On Mon, Dec 06, 2004 at 02:57:02PM -0500, Info wrote:
> Why is spamd running with a home directory under /tmp ?
The debug output you've shown is the initial temp message that gets sent
through spamd to "prime the pump", so to speak.
> Dec 6 14:12:13 Pangloss spamd[23172]: debug: ignore: test mes
