[Slaughtered Subject line ALERT: Not sure what this belongs under,
it showed up on my system sort of buggered up]
Bryan Hoover <[EMAIL PROTECTED]> writes:
[...]
>> STDOUT. If you specify -D and -d together, then spamd should
>> definitely install
>> a $SIG{__WARN__} handler which redirects to its logmsg() function.
>> Actually, it
>> should do this if you use -d whether or not you use -D.
I don't think it does though. All I see with both -d and -D engaged
is ther logmsg output in /var/log/messages `clean message' or similar.
None of the Debug output shows up. So I think logmsg does not handle
debug output. Is this correct?
Bart Schaefer <[EMAIL PROTECTED]> writes:
[...]
> Procmail does nothing more than pass its own stderr descriptor along to
> any sub-process that it starts. The only thing special about procmail is
> that you can use the rc file to tell it where to point its own stderr.
> (You do that by assigning a file name to the LOGFILE variable.)
> > On Wed, 5 Jun 2002, Bryan Hoover wrote:
Not sure what you mean by `warning' but reiterating Barts comments a
little more fully, the debug output is dropped if you have procmail
using spamc and are running spamd with -d -D options. However if you
run as spammassassin in procmail and set procmails LOGFILE variable to
a file name and VERBOSE to YES, then the spamassassin -D output will
show up in the procmail.log set in LOGFILE.
--
LOGFILE=~/.procmail.log
VERBOSE=YES
--
Using Barts' example:
> LOGFILE=/some/log/file
> :0
> | spamassassin -P
If you make that:
LOGFILE=/some/log/file
VERBOSE=YES
:0
| spamassassin -P -D
You should get lots of Debug output in /some/log/file
I add another little thing to procmail to grab the message id since
spamassissin -D for some crazy reason doesn't.
In .procmailrc:
TRAP='formail -XMessage-Id: && date +"%b %d %T%nSTOP"'
Will put the message-ID, date and STOP at the end of processing of
each message. The STOP was just for homeboy parsing tools to quickly
spit out a section from .procmail.log. (procscn.pl)
A home made perl script that searches regular or compressed
procmail.log file and spits out the processing section for a specific
message id.
Or as someone else posted a day or two ago, you could start spamd like
spamd -D [but not -d] > file 2>&1 &
It would run in the background and all msglog and debug info would go
to `file'. Only thing missing is a time stamp (and a msgid) (see bug
393)
_______________________________________________________________
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
