On Tue, 2009-09-08 at 09:08 -0700, John Hardin wrote: > On Tue, 8 Sep 2009, Clunk Werclick wrote: > > > 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 > > That looks like the system log file (/var/log/messages). Have you looked > in the mail log file (typically /var/log/maillog) ? I have it now - the only disappointment for me is it does not log the 'to' or 'from' or client ip. I understand this is not a function of Spamassassin, but it would have been so useful. It's an odd situation perhaps. Blocking at the SMTP stage using a milter in response to a Fetchmail hash feeding Postfix. The result is you see nothing very useful in the logs to identify the blocked message. I trust the set up entirely, but I love my logs too :-)
It's not the fault of SpamAssassin - I'm clear on that, but as it is scanning the entire message retrieved by Fetchmail, it would be really useful to get it to log the client ip, to and from as well. There may even be a hack to do this someone is aware of? -- ----------------------------------------------------------- C Werclick .Lot Technical incompetent Loyal Order Of The Teapot. This e-mail and its attachments is intended only to be used as an e-mail and an attachment. Any use of it for other purposes other than as an e-mail and an attachment will not be covered by any warranty that may or may not form part of this e-mail and attachment.
