> This is probably a dumb question, but my looking through > the docs is just confusing me. > > Can I get SpamAssassin to fully log what it is doing? The > best I can ever get is something like this; > > Mon Aug 3 06:27:57 2009 [4290] info: logger: removing > stderr method Mon Aug 3 06:27:58 2009 [4292] info: > spamd: server started on port 783/tcp (running version > 3.2.5) > Mon Aug 3 06:27:58 2009 [4292] info: spamd: server pid: > 4292 > Mon Aug 3 06:27:58 2009 [4292] info: spamd: server > successfully spawned child process, pid 4293 > Mon Aug 3 06:27:58 2009 [4292] info: spamd: server > successfully spawned child process, pid 4294 > Mon Aug 3 06:27:58 2009 [4292] info: prefork: child > states: SI > Mon Aug 3 06:27:58 2009 [4292] info: prefork: child > states: II > Mon Aug 3 06:34:31 2009 [4292] info: spamd: server > killed by SIGTERM, shutting down > > > But never any actual information on the mail scanning > process. The problem, from my perspective, is I reject > with a milter at the SMTP stage - so I never get to see > any blocked messages. I have a few in my logs that > Fetchmail has picked up from a pop account, before > dumping them into Postfix - and I have no Spamassassin > log I can view to see what they caught on and if I need > to take any action. > > I had a look at: > Mail::SpamAssassin::Logger - SpamAssassin logging module > > But I'm not entirely sure how to invoke that or if I can > get it to give me what I need. It is very terse in > information. > > Perhaps I can start SA differently to produce a log of > the scanning it is doing? I'm sure this is a beginners > question and I feel very stupid having to ask - but I > cannot find the obvious answer.
SA logs to local3.info, not mail.info, in my configuration. I do not recall changing that, it may be default. Does your logger catch local3.info?
