https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6127
--- Comment #16 from Joel <[email protected]> 2009-06-10 10:58:40 PST --- (In reply to comment #12) > > Thanks. Do you have a sample logging module? I am sure I can come up with > > one > > but I am running a production system and it would be helpful to have a > > sample > > from the experts to minimize problems. > Are we talking about sub-spamassassin.pl in qmail-scanner? > It is not calling SpamAssassin directly, but just forking > a spamc and feeding mail to it through a pipe. So as far as > SpamAssassin is concerned, this is a classical spamc/spamd setup. > All your logging is controlled by command line options on spamd, > see its man page. You may want to run it non-daemonized, > with -D or --debug=all, --syslog=stderr, perhaps with stdout > and stderr jointly redirected to some file. I experimented with sa-spamd last night. I had a bit of trouble getting the results specified in the man page, but this morning I did notice that spamd was logging to /var/log/debug.log. # Set defaults : ${spamd_enable:="NO"} : ${spamd_flags="-c -Q --debug all -s /var/log/spamd.log"} : ${spamd_nice="5"} My review of the logs revealed Bug 6122, https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6122 which I fixed by commenting out the line as indicated. I also noticed something akin to Bug 497898 where spamd complains that pyzor is not installed, yet it is. I uploaded a zip file from debug.log detailing all log entries for a pid that crashed. This occured after I commented out the offending line in DKIM. -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
