Sorry I took so long to respond to this. Of course it was me who
should RTFM :-P Since we are using CGPSA we are not using SPAMD if I
understand it right. From the CGPSA website ( http://
www.tffenterprises.com/cgpsa/ ):
"The filter works efficiently, by directly using the SpamAssassin
API. It does not rely on a daemon process such as spamd or on the
execution of shell scripts (as the usual process for utilizing
SpamAssassin with CommuniGate servers does)."
I guess what I saw in our old logs must have been from tests with
SPAMD, unless something changed between versions (I upgraded CGPSA
and SA at the same time).
Thanks for your help Theo and John, much appreciated. I also got to
agree with Kurt about the possibility for SA to write to syslog. It
would help to analyze and adjust SA if you could pull out some
statistics (or is that possible another way?).
Thomas
7 sep 2006 kl. 18.33 skrev Theo Van Dinter:
On Thu, Sep 07, 2006 at 09:11:22AM -0700, John D. Hardin wrote:
[server]spamassassin --lint -D
[22110] dbg: logger: adding facilities: all
[22110] dbg: logger: logging level is DBG
<snip>
Is your syslog daemon configured to discard debug-level messages?
[...]
At last check, spamassassin doesn't log to syslog. spamd does.
--
Randomly Generated Tagline:
"... advise the users that although it can help, they are known
problems ..."
- Stanislav Meduna
Here's our setup: OSX 10.3.9, Communigate 4.2.8, CGPSA 1.4, SA 3.1.3
