https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6127
--- Comment #11 from Joel <[email protected]> 2009-06-09 20:05:04 PST --- (In reply to comment #4) > > 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 => ..., )) 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. -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
