Jeff,
> Thanks for the patch Mark. I'll put it in production tomorrow.
For your purpose, you want to run it with option '-d info', e.g.:
# amavisd -d info
which will give you the 'info'-level debug at amavisd log level 1
or above (set: $log_level=1);
With the next version I'll make the '-d in
> 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 bef
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. Thankfull
> When SpamAssassin is invoked by amavisd, the SA debug log goes to
STDERR.
> There is currently no configurable way to let amavisd hook into SA
logging
> and capture its output, although it is doable and on a TODO list.
> For the moment you can redirect STDERR to a file and let it running
> for a
Jeff,
> I'm working on a SpamAssassin plugin for a university research project.
> I've debugged a lot of it by running SpamAssassin from the command line,
> and using the SA logger's dbg() and info() methods to output stuff.
>
> Now I need to put it in a production server and see the same debug
>
I'm working on a SpamAssassin plugin for a university research project.
I've debugged a lot of it by running SpamAssassin from the command line,
and using the SA logger's dbg() and info() methods to output stuff.
Now I need to put it in a production server and see the same debug
information in the
