https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6127
--- Comment #4 from Mark Martinec <[email protected]> 2009-06-09 11:25:45 PST --- > What is the best way to obtain a full debugging output? Debugging is set to > true in qmail-scanner-queue.pl. The log qmail-queue.log does not contain any > additional information. Is there some docs on this topic? This seems to be a question specific to qmail-scanner, you may get a better answer about logging there. As far as SpamAssassin is concerned, its logging is controlled by an option 'debug' as passed in a hash of options during a call to Mail::SpamAssassin::new, such as: my($sa_obj) = Mail::SpamAssassin->new({debug=>'all', ...}); See man page: 'man Mail::SpamAssassin'. Debugging goes normally to stderr, but can be captured by a caller by supplying a logging module name in a call to: Mail::SpamAssassin::Logger::add(method => ..., )) I'm sorry but I have no idea how qmail-scanner controls the logging. Btw, since you are on FreeBSD where there is no major drama to manually install perl modules, and later revert back to re-installing them from ports if necessary, you may want to try it with SpamAssassin 3.3 from CVS or a tarball. It should still be upwards and downwards compatible with 3.2.5 in practically all aspects. To make it compatible with FreeBSD ports version, two soft links should be added to make life more comfortable: ln -s /usr/local/etc/mail/spamassassin /etc/mail/spamassassin ln -s /var/db/spamassassin /var/lib/spamassassin The installation is as usual: perl Makefile.PL; make; make install and then not to forget to run sa-update. To revert back to SpamAssassin 3.2.5 from ports: pkg_delete -f bsdpan-Mail-SpamAssassin-3.003000 cd /usr/ports/mail/p5-Mail-SpamAssassin/ make; make deinstall; make reinstall; make clean -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
