Increase spamassassin -r verbosity?

[Kārlis Repsons <ka...@gmail.com>]

People,
I'd appreciate a pointer how should spamassassin -r be made more verbose, so 
that it'd report also messages with priority "info", but not "dbg"...

Re: Increase spamassassin -r verbosity?

[Mark Martinec <Ma...@ijs.si>]

On Wednesday February 17 2010 09:50:24 Kārlis Repsons wrote:
> >  spamassassin --debug info -r <msg
> Does the thing, but with one trouble: those info-level messages appear to
> be directed through stderr! Can they be directed through stdout, while
> warning messages through stderr?

That's the best we can offer with 3.3.0 and earlier.
I suggest to open a bugzilla ticket, requesting a --verbose option
to spamassassin -r.

  Mark

Re: Increase spamassassin -r verbosity?

[Kārlis Repsons <ka...@gmail.com>]

On Wednesday 17 February 2010 12:09:50 Frank Heydlauf wrote:
> Hi K??rlis,
> 
> On Wed, Feb 17, 2010 at 08:50:24AM +0000, K??rlis Repsons wrote:
> > On Tuesday 16 February 2010 18:18:01 Mark Martinec wrote:
> 
> ...
> 
> > >   spamassassin --debug info -r <msg
> 
> ...
> 
> > Does the thing, but with one trouble: those info-level messages appear to
> > be directed through stderr! Can they be directed through stdout, while
> > warning messages through stderr?
> 
> if it's only a question of stderr or stdout, just
> redirect stderr to stdout.
> 
> spamassassin --debug -r <msg 2>&1
cat spammessage | (sudo -u $user $maildroppath -d $user report_gross_spam > /dev/null) 2>&1 | sed "/^\[[0-9]*\][ ]*info: .*/d"
And maildrop script contains:  cc "| spamassassin --debug info -r"

Is how I actually solved the problem for now... (ah tickets, yes, I should...)

Re: Increase spamassassin -r verbosity?

[Frank Heydlauf <fh...@lf.net>]

Hi K??rlis,

On Wed, Feb 17, 2010 at 08:50:24AM +0000, K??rlis Repsons wrote:
> On Tuesday 16 February 2010 18:18:01 Mark Martinec wrote:
...
> >   spamassassin --debug info -r <msg
...
> Does the thing, but with one trouble: those info-level messages appear to be 
> directed through stderr! Can they be directed through stdout, while warning 
> messages through stderr?

if it's only a question of stderr or stdout, just 
redirect stderr to stdout.

spamassassin --debug -r <msg 2>&1

-- 
Regards
Frank

Re: Increase spamassassin -r verbosity?

[Kārlis Repsons <ka...@gmail.com>]

On Tuesday 16 February 2010 18:18:01 Mark Martinec wrote:
> > > I'd appreciate a pointer how should spamassassin -r be made more
> > > verbose, so that it'd report also messages with priority "info", but
> > > not "dbg"...
> >
> > spamassassin --debug area=noall -r <msg
> 
> Sorry, wrong syntax, should be:
>   spamassassin --debug noall -r <msg
> or
>   spamassassin --debug info -r <msg
> 
> Mark

Does the thing, but with one trouble: those info-level messages appear to be 
directed through stderr! Can they be directed through stdout, while warning 
messages through stderr?

Re: Increase spamassassin -r verbosity?

[Mark Martinec <Ma...@ijs.si>]

> > I'd appreciate a pointer how should spamassassin -r be made more verbose,
> > so that it'd report also messages with priority "info", but not "dbg"...
> 
> spamassassin --debug area=noall -r <msg

Sorry, wrong syntax, should be:
  spamassassin --debug noall -r <msg
or
  spamassassin --debug info -r <msg

Mark

Re: Increase spamassassin -r verbosity?

[Mark Martinec <Ma...@ijs.si>]

Kārlis,


> I'd appreciate a pointer how should spamassassin -r be made more verbose,
> so that it'd report also messages with priority "info", but not "dbg"...

spamassassin --debug area=noall -r <msg


  Mark