> Jeff, > > What I was hoping to do was write stuff to the log file for a week or > > two using the info() method. Then I could grep out my lines, get > > the data analyzed, and then finish the plugin. > > > > I am a fairly experienced programmer but I have not used object oriented > > Perl before. Thankfully it doesn't seem that different from other OO > > languages. Anyway I don't mind hacking up a temporary version of > > Amavisd if you could tell me how to get SA to quit logging to STDERR. > > Ok, here is a patch to amavisd-new 2.5.2 (works with SA 3.2.3), which > achieves what you need, or at least should get you going. It hooks > its own logging module into SpamAssassin, so it receives all logging > from SA. It maps SpamAssassin log levels into amavisd log levels > (which in turn are mapped into syslog priorities), so you should > be seing for example SA 'info:' at amavisd log level 1, and 'dbg:' > at log level 5 (so you must have $log_level=5 in order to see dbg:). > Change the mapping to taste if you like.
-------------------snip snip snip---------------------- Thanks for the patch Mark. I'll put it in production tomorrow. Could you please take a minute to explain the underlying issue to me. I don't understand why SA does not log without the patch. Is SA intentionally logging to STDERR, or is Amavisd's connection to syslog causing SA to loose it's connection. Jeff Moss
